From: Tom Lane <tgl@sss.pgh.pa.us>
To: wolakk@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17598: EXTENSION can no longer create it's own schema!
 (Create Schema IF NOT EXISTS XXX)
In-reply-to: <17598-90d4e2f6057cbfec@postgresql.org>
References: <17598-90d4e2f6057cbfec@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sun, 28 Aug 2022 21:30:01 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3136391.1661780319.1@sss.pgh.pa.us>
Date: Mon, 29 Aug 2022 09:38:39 -0400
Message-ID: <3136392.1661780319@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3136392.1661780319%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Effectively if FEELS like the check for an schema/extension
> "owning/belonging to" a schema/extension is failing.
> In this case, the schema DOES NOT EXIST.  And the create if not exists
> FAILS! (Which feels like an edge case.

This is an intentional change to close a security hole: it is unsafe for
an extension script to use CREATE IF NOT EXISTS this way.  (What if
a hostile attacker created the schema?  Now you are depending on a
schema that the attacker has ownership privileges on.)  Drop the
IF NOT EXISTS clause, if you're expecting the extension to create the
schema.

			regards, tom lane