Skip site navigation (1) Skip section navigation (2)

Re: Re: BUG #6264: Superuser does not have inherent Replication permission

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Keith Fiske <keith(at)omniti(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: BUG #6264: Superuser does not have inherent Replication permission
Date: 2011-10-28 13:32:30
Message-ID: CA+Tgmobob84JT8Bb50wNa5kheyU=r2k9x3pQAtkiGhcJGTMC_A@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Thu, Oct 27, 2011 at 6:15 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Noah Misch <noah(at)leadboat(dot)com> writes:
>> Let's look at the behavior of DDL-exposed access constraints for precedent.  We
>> currently have three paradigms for applying access control to superusers:
>
>> 1. Settings that affect superusers and regular users identically.  These include
>> ALTER ROLE ... LOGIN | VALID UNTIL.
>
>> 2. Rights that superusers possess implicitly and irrevocably; the actual setting
>> recorded in pg_authid or elsewhere has no effect.  These include GRANT ... ON
>> TABLE and ALTER ROLE ... CREATEDB | CREATEROLE.
>
>> 3. ALTER ROLE ... REPLICATION is very similar to #1, except that CREATE ROLE
>> ... SUPERUSER implies CREATE ROLE ... SUPERUSER REPLICATION.
>
>> I think we should merge #3 into #2; nothing about the REPLICATION setting
>> justifies a distinct paradigm.
>
> Yeah, there's much to be said for that.  I thought the notion of a
> privilege that superusers might not have was pretty bogus to start with.
>
> rolcatupdate isn't a very good precedent to rely on because it's never
> been documented or used to any noticeable extent, so there's no reason
> to think that it provides a tested-and-accepted behavior.

That seems fine for 9.2, but I am still not in favor of changing the
behavior in back branches.  This is not such a confusing behavior that
we can't document our way out of it.

(Hey, if SELECT .. ORDER BY .. FOR UPDATE can return rows out of order
and we can document our way out of that, this is small potatoes by
comparison.)

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-bugs by date

Next:From: Alvaro HerreraDate: 2011-10-28 13:39:40
Subject: Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"
Previous:From: Robert YoungDate: 2011-10-28 07:11:57
Subject: Re: Add statistics_collector_listen_addresses to fix hard-coding of "localhost"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group