Re: [PG19] CREATE SCHEMA puts an index or trigger on a same-named temp table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>
Subject: Re: [PG19] CREATE SCHEMA puts an index or trigger on a same-named temp table
Date: 2026-10-22 17:22:00
Message-ID: 2536395.1792689720@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

shihao zhong <zhong950419(at)gmail(dot)com> writes:
> In v18 an unqualified CREATE SCHEMA element got the new schema's name
> filled in. a9c350d9e stopped doing that, and the revert in 962e0a723
> (e0fdc3f54b4 in 19) kept it.
> So the name now goes through search_path, where pg_temp comes first:

Ooops, good catch. The patch needed some more work on comments,
and I also chose to go back to the old function naming
"setSchemaName..." instead of "checkSchemaName...", but the functional
correction is fine. Pushed.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-10-22 17:52:40 Re: [PG19] CREATE SCHEMA puts an index or trigger on a same-named temp table
Previous Message Andrey Borodin 2026-10-22 16:42:53 Let physical WAL senders restore missing segments from the archive