Re: security_definer_search_path GUC

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Joel Jacobson <joel(at)compiler(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: security_definer_search_path GUC
Date: 2021-06-04 16:03:05
Message-ID: CAFj8pRD=C8KV67k_F7Uwa4HYO28DLRK329p5O6Zd_=CViaL2nQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards

Pavel

/Joel
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2021-06-04 16:04:02 Re: Incorrect usage of strtol, atoi for non-numeric junk inputs
Previous Message Joel Jacobson 2021-06-04 15:42:29 Re: security_definer_search_path GUC