| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Removing pg_pltemplate and creating "trustable" extensions |
| Date: | 2020-01-13 20:38:59 |
| Message-ID: | 28604.1578947939@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> In the meantime, though, this idea as stated doesn't do anything except
>> let a DB owner grant install privileges to someone else. I'm not even
>> convinced that we want that, or that anyone needs it (I can recall zero
>> such requests related to PLs in the past). And for sure it does not
>> belong in a minimal implementation of this feature.
> Yes, that's what this approach would do. I suppose an alternative would
> be to lump it in with "CREATE" rights on the DB, but I've advocated and
> will continue to advocate for splitting up of such broad rights.
> DB-level CREATE rights currently cover both schemas and publications,
> for example, even though the two have rather little to do with each
> other.
The patch as I'm proposing it has nothing to do with "CREATE" rights.
You're attacking something different from what I actually want to do.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anastasia Lubennikova | 2020-01-13 20:49:36 | Re: Building infrastructure for B-Tree deduplication that recognizes when opclass equality is also equivalence |
| Previous Message | Tom Lane | 2020-01-13 20:36:34 | Re: BUG #16059: Tab-completion of filenames in COPY commands removes required quotes |