|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Stephen Frost <sfrost(at)snowman(dot)net>|
|Cc:||Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>|
|Subject:||Re: Removing pg_pltemplate and creating "trustable" extensions|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
>> On Tue, Jan 28, 2020 at 16:17 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> On the other hand, there's the point that lots of people have probably
>>> given out schema-CREATE privilege to users whom they wouldn't necessarily
>>> wish to trust with INSTALL privilege. Schema-CREATE is a pretty harmless
>>> privilege, INSTALL much less so.
>> CREATE doesn't just control the ability to create schemas these days- it
>> was extended to cover publications also not that long ago.
> Oh really ... hm, that does make it a much bigger deal than I was
> thinking. Given that, I don't think there's any huge objection to
> attaching this to CREATE, at least till we get around to a more
> significant redesign.
Here's a v5 that drops the new predefined role and allows
trusted-extension installation when you have CREATE on the current
database. There's no other changes except a bit of documentation
Barring further complaints, I'm going to push this fairly soon.
regards, tom lane
|Next Message||Robert Haas||2020-01-29 18:41:39||Re: Enabling B-Tree deduplication by default|
|Previous Message||Robert Haas||2020-01-29 18:16:05||Re: [Proposal] Global temporary tables|