Re: BUG #6264: Superuser does not have inherent Replication permission
От | Magnus Hagander |
---|---|
Тема | Re: BUG #6264: Superuser does not have inherent Replication permission |
Дата | |
Msg-id | CABUevEyAUcq+AG4QMdoAEodNFJZ6Wfk-jQ1OpyihWft+SDFb8A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #6264: Superuser does not have inherent Replication permission (Keith Fiske <keith@omniti.com>) |
Ответы |
Re: BUG #6264: Superuser does not have inherent Replication permission
Re: BUG #6264: Superuser does not have inherent Replication permission |
Список | 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 по дате отправления: