| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <me(at)jeltef(dot)nl> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extension security improvement: Add support for extensions with an owned schema |
| Date: | 2024-06-20 17:02:36 |
| Message-ID: | A313D9D2-E258-4FD6-9B80-647130B75B92@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jun 19, 2024, at 13:50, Jelte Fennema-Nio <me(at)jeltef(dot)nl> wrote:
> This indeed does sound like the behaviour that pretty much every
> existing extension wants to have. One small addition/clarification
> that I would make to your definition: fully qualified references to
> other objects should still be allowed.
Would be tricky for referring to objects from other extensions with no defined schema, or are relatable.
> 1. To have a safe search_path that can be used in SET search_path on a
> function (see also [1]).
> 2. To make it easy for extension authors to avoid conflicts with other
> extensions/UDFs.
These would indeed be nice improvements IMO.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2024-06-20 17:02:41 | Re: Direct SSL connection and ALPN loose ends |
| Previous Message | David E. Wheeler | 2024-06-20 17:00:41 | Re: Extension security improvement: Add support for extensions with an owned schema |