| From: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
|---|---|
| To: | "Koshi Shibagaki (Fujitsu)" <shibagaki(dot)koshi(at)fujitsu(dot)com>, Junwang Zhao <zhjwpku(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CREATE TABLE .. LIKE copies comments to an unrelated table |
| Date: | 2026-10-13 13:34:12 |
| Message-ID: | 8f900da8-1bbb-414b-ba15-e51bf0f13175@uni-muenster.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lucas Jeffrey | 2026-10-13 13:36:32 | Re: Re: [PATCH] Fix segmentation fault caused by reentrancy in RI_Fkey_cascade_del (ri_triggers.c) |
| Previous Message | Robert Haas | 2026-10-13 13:28:06 | Re: CREATE OR REPLACE MATERIALIZED VIEW |