From: Tom Lane <tgl@sss.pgh.pa.us>
To: Darafei "Komяpa" Praliaskouski <me@komzpa.net>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Marking some contrib modules as trusted extensions
Date: Wed, 29 Jan 2020 16:27:08 -0500
Message-ID: <4750.1580333228@sss.pgh.pa.us> (raw)
In-Reply-To: <CAC8Q8tKiedws=GNF_M50tV7qw7TJ0y_=+k+WJHPNc=VqScZr5A@mail.gmail.com>
References: <32315.1580326876@sss.pgh.pa.us>
<CAC8Q8tKiedws=GNF_M50tV7qw7TJ0y_=+k+WJHPNc=VqScZr5A@mail.gmail.com>
=?UTF-8?Q?Darafei_=22Kom=D1=8Fpa=22_Praliaskouski?= <me@komzpa.net> writes:
>> btree_gin
>> btree_gist
> I would even ask btree_gin and btree_gist to be moved to core.
That's not in scope here. Our past experience with trying to move
extensions into core is that it creates a pretty painful upgrade
experience for users, so that's not something I'm interested in doing
... especially for relatively marginal cases like these.
There's also a more generic question of why we should want to move
anything to core anymore. The trusted-extension mechanism removes
one of the biggest remaining gripes about extensions, namely the
pain level for installing them. (But please, let's not have that
debate on this thread.)
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, me@komzpa.net, pgsql-hackers@lists.postgresql.org
Subject: Re: Marking some contrib modules as trusted extensions
In-Reply-To: <4750.1580333228@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox