Re: Streaming replication as a separate permissions

Magnus Hagander <magnus@hagander.net>

From: Magnus Hagander <magnus@hagander.net>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter_e@gmx.net>, Stephen Frost <sfrost@snowman.net>, Florian Pflug <fgp@phlo.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-01-03T22:50:35Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Allow Win32 to compile under MinGW. Major changes are:

On Mon, Jan 3, 2011 at 17:23, Robert Haas <robertmhaas@gmail.com> wrote:
> On Mon, Jan 3, 2011 at 11:20 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Robert Haas <robertmhaas@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?


-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/