Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)
Date
Msg-id 3136392.1661780319@sss.pgh.pa.us
Whole thread Raw
In response to BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Richard Guo
Date:
Subject: Re: foreign join error "variable not found in subplan target list"
Next
From: Amit Kapila
Date:
Subject: Re: BUG #17594: conditional hash indexes size (hash index ignore WHERE condition during CREATE INDEX?)