Re: Extension security improvement: Add support for extensions with an owned schema

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Jelte Fennema-Nio <me(at)jeltef(dot)nl>
Cc: 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 15:51:08
Message-ID: CA+Tgmoao8nO9g4ZmqMRKmtkD3qLS8OxA-VmvjhAAXoAX96kxZA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 19, 2024 at 1:50 PM Jelte Fennema-Nio <me(at)jeltef(dot)nl> wrote:
> I do think, even if we have this, there would be other good reasons to
> use "owned schemas" for extension authors. At least the following two:
> 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.

(1) is a very good point. (2) I don't know about one way or the other.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2024-06-20 16:01:11 Re: SQL/JSON query functions context_item doc entry and type requirement
Previous Message Chapman Flack 2024-06-20 15:49:18 Re: jsonpath Time and Timestamp Special Cases