| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Darafei "Komяpa" Praliaskouski <me(at)komzpa(dot)net> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Marking some contrib modules as trusted extensions |
| Date: | 2020-01-29 21:27:08 |
| Message-ID: | 4750.1580333228@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?UTF-8?Q?Darafei_=22Kom=D1=8Fpa=22_Praliaskouski?= <me(at)komzpa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2020-01-29 21:28:22 | Re: Marking some contrib modules as trusted extensions |
| Previous Message | Mark Dilger | 2020-01-29 21:06:35 | Re: making the backend's json parser work in frontend code |