Re: BUG #6264: Superuser does not have inherent Replication permission - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: BUG #6264: Superuser does not have inherent Replication permission
Date
Msg-id CABUevEyAUcq+AG4QMdoAEodNFJZ6Wfk-jQ1OpyihWft+SDFb8A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #6264: Superuser does not have inherent Replication permission  (Keith Fiske <keith@omniti.com>)
Responses Re: BUG #6264: Superuser does not have inherent Replication permission  (Simon Riggs <simon@2ndQuadrant.com>)
Re: BUG #6264: Superuser does not have inherent Replication permission  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
On Mon, Oct 24, 2011 at 16:37, Keith Fiske <keith@omniti.com> wrote:
> On Sat, Oct 22, 2011 at 11:49 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> "Keith Fiske" <keith@omniti.com> writes:
>
>>> If you create a user as a NONsuperuser,
>>> then later ALTER them to be one, they will NOT have the replication
>>> permission and cannot be used as a replication user until you explicitly
>>> grant that permission.
>>
>> That doesn't sound to me like a bug. =A0These flags are independent, we
>> just provide a certain default at role creation time.
>>
>
> That is not what the documentation as read would lead people to
> believe. I'd be more than happy to help with clarifying the
> documentation myself if needed. Just let me know how.

This part I agree with - it makes sense for ALTER to set both flags
when it enables superuser. It seems inconsistent now - even if it may
be technically correct.

If we don't change it, we should definitely accept a docs patch to
clarify what happens, because I agree it's confusing.

--=20
=A0Magnus Hagander
=A0Me: http://www.hagander.net/
=A0Work: http://www.redpill-linpro.com/

pgsql-bugs by date:

Previous
From: John R Pierce
Date:
Subject: Re: BUG #6266: Create temp tables on Slave
Next
From: Simon Riggs
Date:
Subject: Re: BUG #6264: Superuser does not have inherent Replication permission