| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Darafei Komяpa Praliaskouski <me(at)komzpa(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Marking some contrib modules as trusted extensions |
| Date: | 2020-01-29 21:28:22 |
| Message-ID: | CAOBaU_YcmiKnLvb8kpLNA59Di9WA02V3_TCfJ8pAMriPfeRq_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 29, 2020 at 9:46 PM Darafei "Komяpa" Praliaskouski
<me(at)komzpa(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-29 21:38:53 | Re: Marking some contrib modules as trusted extensions |
| Previous Message | Tom Lane | 2020-01-29 21:27:08 | Re: Marking some contrib modules as trusted extensions |