| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: security_definer_search_path GUC |
| Date: | 2021-06-07 21:09:18 |
| Message-ID: | CAKFQuwaHKTugicKMdJShdXMAnpC=Vx2rM+KvncyJW+mp9ATvog@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 4, 2021 at 9:03 AM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:
> pá 4. 6. 2021 v 17:43 odesílatel Joel Jacobson <joel(at)compiler(dot)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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2021-06-07 21:22:36 | Re: security_definer_search_path GUC |
| Previous Message | Alvaro Herrera | 2021-06-07 21:07:34 | Re: Add PortalDrop in exec_execute_message |