From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Streaming replication as a separate permissions |
Date: | 2010-12-27 13:25:29 |
Message-ID: | 1293456329.1193.63371.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2010-12-27 at 12:00 +0100, Magnus Hagander wrote:
> On Mon, Dec 27, 2010 at 11:34, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> > On Mon, 2010-12-27 at 10:36 +0100, Magnus Hagander wrote:
> >> > Is backup part of this new privilege, or not?
> >>
> >> The "integrated base backup", once we have that, that's based on the
> >> walsender protocol? yes.
> >> pg_dump style backups? No.
> >
> > Where does pg_start_backup()/stop fit?
>
> Good question :)
>
> Given that the integrated-base-backup would call it for you, that one
> would definitely get it automatically.
>
> Given that the latest discissions seem to have most people wanting the
> replication role *not* to be allowed to log in and run general SQL, we
> should not drive the start/stop backup permissions from that
> privilege.
So what your suggesting would actually defeat the purpose of having the
new privilege. Unless we trust in a new, untried method. Hmmm.
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2010-12-27 13:39:02 | Re: Recovery conflict monitoring |
Previous Message | Pavel Stehule | 2010-12-27 12:27:51 | Re: MULTISET patch |