Re: Marking some contrib modules as trusted extensions - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Marking some contrib modules as trusted extensions
Date
Msg-id CAOBaU_YcmiKnLvb8kpLNA59Di9WA02V3_TCfJ8pAMriPfeRq_w@mail.gmail.com
Whole thread Raw
In response to Re: Marking some contrib modules as trusted extensions  (Darafei "Komяpa" Praliaskouski <me@komzpa.net>)
Responses Re: Marking some contrib modules as trusted extensions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jan 29, 2020 at 9:46 PM Darafei "Komяpa" Praliaskouski
<me@komzpa.net> wrote:
>
> Hello,
>
>>
>> btree_gin
>> btree_gist
>
>
> I would even ask btree_gin and btree_gist to be moved to core.

Without going that far, I also agree that I relied on those extension
quite often, so +1 for marking them as trusted.

>> Probably NO, if only because you'd need additional privileges
>> to use these anyway:
>> pg_stat_statements

But the additional privileges are global, so assuming the extension
has been properly setup, wouldn't it be sensible to ease the
per-database installation?  If not properly setup, there's no harm in
creating the extension anyway.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Marking some contrib modules as trusted extensions
Next
From: Tom Lane
Date:
Subject: Re: Marking some contrib modules as trusted extensions