From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexey Bashtanov <bashtanov(at)imap(dot)cc>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #9923: "reassign owned" does not change permissions grantor |
Date: | 2015-12-21 22:54:50 |
Message-ID: | 20151221225450.GZ2618@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Bruce Momjian wrote:
> On Thu, Dec 17, 2015 at 03:21:46PM -0500, Tom Lane wrote:
> > Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > > Backpatching seems fine to me. I was just concerned if anyone was
> > > relying on the existing buggy behavior.
> >
> > Seems unlikely. Even if they are, the potential for catalog corruption
> > later seems to trump that argument.
> >
> > > We do list this item as a 9.5
> > > incompatibility, so the question is whether we can add an
> > > incompatibility to back branches:
> >
> > > Fix <link linkend="SQL-REASSIGN-OWNED"><command>REASSIGN OWNED</></>
> > > and <link linkend="SQL-ALTERTYPE"><command>ALTER OWNER TO</></>
> > > to properly update permissions lists (ACLs) when changing ownership of
> > > types, foreign data wrappers, and foreign servers (Bruce Momjian)
> >
> > Actually, I guess we should take out that 9.5 release note item altogether
> > if we back-patch this.
>
> Yes, that was one of my points.
Backpatched all the way back to 9.1. Are you, Bruce, on the hook for
removing the 9.5 release note entry, or should I do that?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-12-21 23:15:36 | Re: GIN index isn’t working with intarray |
Previous Message | Maeldron T. | 2015-12-21 22:18:15 | GIN index isn’t working with intarray |