Horton

Re: Marking some contrib modules as trusted extensions

Julien Rouhaud <rjuju123@gmail.com>

View thread View on postgr.es
From: Julien Rouhaud <rjuju123@gmail.com>
To: Darafei Komяpa Praliaskouski <me@komzpa.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2020-01-29T21:28:22Z
Lists: 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.

Commits

  1. Remove support for upgrading extensions from "unpackaged" state.

  2. Mark some contrib modules as "trusted".

  3. Invent "trusted" extensions, and remove the pg_pltemplate catalog.