Horton

Re: Streaming replication as a separate permissions

Magnus Hagander <magnus@hagander.net>

View thread
From: Magnus Hagander <magnus@hagander.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>, Robert Haas <robertmhaas@gmail.com>, Florian Pflug <fgp@phlo.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-12-27T15:40:10Z
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, Dec 27, 2010 at 16:33, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> On Mon, Dec 27, 2010 at 10:53, Magnus Hagander <magnus@hagander.net> wrote:
>>> We could quite easily make a replication role *never* be able to
>>> connect to a non-walsender backend. That would mean that if you set
>>> your role to WITH REPLICATION, it can *only* be used for replication
>>> and nothing else (well, you could still SET ROLE to it, but given that
>>> it's not a superuser (anymore), that doesn't have any security
>>> implications.
>
>> Actually, having implemented that and tested it, I realize that's a
>> pretty bad idea.
>
> OK, so if we're not going to recommend that REPLICATION roles be
> NOLOGIN, we're back to the original question: should the REPLICATION
> bit give any other special privileges?  I can see the point of allowing
> such a user to issue pg_start_backup and pg_stop_backup.

Yes, those would definitely be useful.

We are, basically, talking about where we'll relax the "only
superuser" one, right? Since they are normal roles, the DBA can always
GRANT permissions on *objects* to them, but there are superuser-only
things taht you can't GRANT away...


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