Re: security_definer_search_path GUC

Pavel Stehule <pavel.stehule@gmail.com>

From: Pavel Stehule <pavel.stehule@gmail.com>

To: Joel Jacobson <joel@compiler.org>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2021-06-04T16:03:05Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Create a new GUC variable search_path to control the namespace search
- 838fe25a9532 7.3.1 cited

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.

Regards

Pavel

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