On Wed, Jan 5, 2011 at 04:24, Robert Haas <robertmh...@gmail.com> wrote: > On Mon, Jan 3, 2011 at 5:50 PM, Magnus Hagander <mag...@hagander.net> wrote: >> On Mon, Jan 3, 2011 at 17:23, Robert Haas <robertmh...@gmail.com> wrote: >>> On Mon, Jan 3, 2011 at 11:20 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >>>> Robert Haas <robertmh...@gmail.com> writes: >>>>> On the other hand, the REPLICATION privilege is denying you the right to >>>>> perform an operation *even though you already are authenticated as a >>>>> superuser*. I don't think there's anywhere else in the system where >>>>> we allow a privilege to non-super-users but deny that same privilege >>>>> to super-users, and I don't think we should be starting now. >>>> >>>> You might want to reflect on rolcatupdate a bit before asserting that >>>> there are no cases where privileges are ever denied to superusers. >>> >>> Oh, huh. I wasn't aware of that. >>> >>>> However, that precedent would suggest that the default should be to >>>> grant the replication bit to superusers. >>> >>> Yes it would. >> >> Just to be clear: are we saying that "CREATE ROLE foo SUPERUSER" >> should grant both superuser and replication, as well as the default >> "postgres" user also having replication as well? > > I think that's what we're saying.
Ok, done and applied. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
