Re: security_definer_search_path GUC - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: security_definer_search_path GUC
Date
Msg-id CAKFQuwZF6n_LW0Ove1F6LFmoNR5Lh8yxG4OJL38EFjZDEFovHg@mail.gmail.com
Whole thread Raw
In response to Re: security_definer_search_path GUC  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On Mon, Jun 7, 2021 at 2:09 PM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Fri, Jun 4, 2021 at 9:03 AM Pavel Stehule <pavel.stehule@gmail.com> wrote:
pá 4. 6. 2021 v 17:43 odesílatel Joel Jacobson <joel@compiler.org> napsal:
Maybe this could work:
CREATE SCHEMA schema_name UNQUALIFIED;
Which would explicitly make all the objects created in the schema accessible unqualified, but also enforce there are no conflicts with other objects in existence in all unqualified schemas, upon the creation of new objects.

Yes, it can work. I am not sure if "unqualified" is the best keyword, but the idea is workable.

Sounds like a job for an event trigger listening to CREATE/ALTER schema.

Never mind...I got mixed up a bit on what this all is purporting to do.  My intent was to try and solve the problem with existing features (event triggers) instead of inventing new ones, which is still desirable.

David J.

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: security_definer_search_path GUC
Next
From: "David G. Johnston"
Date:
Subject: Re: security_definer_search_path GUC