Re: CREATE SCHEMA still resolves unqualified type names in pg_temp

From: Ayoub Kazar <ayoub(dot)kazar(at)data-bene(dot)io>
To: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: CREATE SCHEMA still resolves unqualified type names in pg_temp
Date: 2026-11-16 00:27:21
Message-ID: dcdec330-af97-4971-8c2b-b525d4149538@data-bene.io
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 15/11/2026 20:45, Jim Jones wrote:
> While experimenting with new code I found something related in IMPORT
> FOREIGN SCHEMA -- it probably deserves its own patch. The cause seems to
> be the same.
That is correct!
> WDYT?
Yeah this deserves a separate patch, I considered if we should create a
helper func to unify search path stuff in schemacmds.c, foreigncmds.c,
and extension.c. But the latter is a bit different and it's not the
right moment for a refactor on them anyways, so i think duplicating and
following extension.c is okay.

Thanks for the review!

Regards,
Ayoub Kazar

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-11-16 00:33:06 Re: psql: Don't offer USING INDEX after REPACK (CONCURRENTLY) or (ANALYZE)
Previous Message Jianqiao Han 2026-11-16 00:00:00 Re: [PATCH] Normalize numeric/bigint scientific notation after rounding