Re: Removing pg_pltemplate and creating "trustable" extensions
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Robert Haas <robertmhaas@gmail.com>,
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-01-13T20:38:59Z
Lists: pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes: > * Tom Lane (tgl@sss.pgh.pa.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
Commits
-
Invent "trusted" extensions, and remove the pg_pltemplate catalog.
- 50fc694e4374 13.0 landed