Re: Streaming replication as a separate permissions
Simon Riggs <simon@2ndquadrant.com>
From: Simon Riggs <simon@2ndQuadrant.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-12-27T13:25:29Z
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 →
-
Allow Win32 to compile under MinGW. Major changes are:
- 12c942383296 7.4.1 cited
On Mon, 2010-12-27 at 12:00 +0100, Magnus Hagander wrote: > On Mon, Dec 27, 2010 at 11:34, Simon Riggs <simon@2ndquadrant.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