Hi Koshi On 13/10/2026 13:57, Koshi Shibagaki (Fujitsu) wrote: > This requires a superuser, and permanent tables can already encounter > the same error when their destination schema is renamed concurrently. > Therefore, if the intention is to match the name-based behavior of permanent > tables, I think this is reasonable.
I see your point there. However, since this requires a superuser, I don't think it needs to be fixed -- a superuser can do a lot of nasty things. Trying to anticipate a superuser renaming a temp schema mid-session is IMHO not something we should worry about. Please let me know if I'm missing something here. Thanks for the review. Much appreciated! Best, Jim
