| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER ... OWNER TO ... vs. ALTER DEFAULT PRIVILEGES |
| Date: | 2015-10-30 23:16:31 |
| Message-ID: | CA+Tgmob7_mHBA8A_3RnicgFP4a5amiV3U_uq26B50fWS3Lzciw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 29, 2015 at 10:31 PM, David Fetter <david(at)fetter(dot)org> wrote:
> Had this been part of the original ALTER DEFAULT PRIVILEGES patch,
> those privileges would simply have been applied. Since it wasn't, I'm
> ass-u-me'ing that changing the default behavior to that is going to
> cause (possibly legitimate) anxiety.
The word "applied" is not very clear here. You want to revoke all
existing privileges and then regrant whatever the default privileges
would have been given the new owner? That might be a reasonable thing
to have a command for, but doing it automatically on an owner change
does not sound like a good idea. That could be very surprising
behavior.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-10-30 23:42:54 | Re: September 2015 Commitfest |
| Previous Message | Filip Rembiałkowski | 2015-10-30 22:06:32 | Re: pg_dump LOCK TABLE ONLY question |