From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Noah Misch <noah(at)leadboat(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, José Luis Tallón <jltallon(at)adv-solutions(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Default Roles |
Date: | 2016-04-18 14:03:29 |
Message-ID: | 20160418140329.GL10850@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Noah Misch (noah(at)leadboat(dot)com) wrote:
> On Thu, Apr 07, 2016 at 03:50:47PM -0400, Stephen Frost wrote:
> > I'm planning to continue going over the patch tomorrow morning with
> > plans to push this before the feature freeze deadline.
>
> > --- a/src/test/regress/expected/rolenames.out
> > +++ b/src/test/regress/expected/rolenames.out
>
> > +GRANT testrol0 TO pg_abc; -- error
> > +ERROR: role "pg_abc" is reserved
> > +DETAIL: Cannot GRANT roles to a reserved role.
>
> The server still accepts "ALTER ROLE testrol0 USER pg_signal_backend". It
> should block this ALTER ROLE if it blocks the corresponding GRANT.
Agreed, I specifically recall looking at that bit of code, but I think I
got myself convinced that it was the other way around (that the ALTER
would end up granting pg_signal_backend to testrol0, which would be
fine), but you're right, this needs to be prevented also.
Will fix.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2016-04-18 14:12:32 | Re: pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
Previous Message | Robert Haas | 2016-04-18 14:03:25 | Re: snapshot too old, configured by time |