Re: PG 13 trusted extensions and pg_available_extensions - Mailing list pgsql-general

From Julien Rouhaud
Subject Re: PG 13 trusted extensions and pg_available_extensions
Date
Msg-id CAOBaU_bo2zZm6-9Hmn-XA0NtYdSMZ1v2A0fAmfX_9tgZZGt1Ng@mail.gmail.com
Whole thread Raw
In response to Re: PG 13 trusted extensions and pg_available_extensions  (Michael Paquier <michael@paquier.xyz>)
Responses Re: PG 13 trusted extensions and pg_available_extensions  ("Daniel Westermann (DWE)" <daniel.westermann@dbi-services.com>)
List pgsql-general
On Thu, Sep 24, 2020 at 10:58 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Wed, Sep 23, 2020 at 03:28:45PM +0000, Daniel Westermann (DWE) wrote:
> > I was playing a bit with trusted extensions and wondered if there is
> > a reason that the "trusted" flag is not exposed in pg_available_extensions.
> > I believe that information would be quite useful so one can easily
> > identify extensions that can be installed as "normal" user.
>
> Adding the trusted flag makes sense for visibility.  There is a bit
> more that we could consider though?  For example, what about
> "relocatable" and "requires"?

+1, and also the schema (for non relocatable extensions).



pgsql-general by date:

Previous
From: Michael Paquier
Date:
Subject: Re: PG 13 trusted extensions and pg_available_extensions
Next
From: Tony Shelver
Date:
Subject: Re: PostgreSQL on Windows' state