| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, 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-28 20:58:28 |
| Message-ID: | CA+Tgmob8d4iaD_nxdmugGbfc=USkm4ZA_NOkY2mK8B6s4oaBMg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 28, 2020 at 3:52 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I continue to think that allowing DB owners to decide this is, if not
> fundamentally the wrong thing, at least not a feature that anybody has
> asked for in the past. The feature *I* want in this area is for the
> superuser to be able to decide who's got install privilege. Making
> it a DB-level privilege doesn't serve that goal, more the opposite.
I agree.
> Still, if we can compromise by making this part of DB "CREATE" privilege
> for the time being, I'm willing to take that compromise. It's certainly
> better than failing to get rid of pg_pltemplate.
Doesn't that have exactly the issue you describe above?
bob=> grant create on database bob to fred;
GRANT
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Zhang | 2020-01-28 20:59:30 | Re: Making psql error out on output failures |
| Previous Message | Robert Haas | 2020-01-28 20:54:35 | Re: [PATCH] Windows port, fix some resources leaks |