Re: PG 13 trusted extensions and pg_available_extensions

From: "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: PG 13 trusted extensions and pg_available_extensions
Date: 2020-09-25 06:51:45
Message-ID: ZR0P278MB012202246010B77B6D8620BAD2360@ZR0P278MB0122.CHEP278.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 24, 2020 at 10:58 AM Michael Paquier <michael(at)paquier(dot)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).

+1

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2020-09-25 08:04:53 Re: Can I get some PostgreSQL developer feedback on these five general issues I have with PostgreSQL and its ecosystem?
Previous Message tutiluren 2020-09-25 05:40:11 Re: Can I get some PostgreSQL developer feedback on these five general issues I have with PostgreSQL and its ecosystem?