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-27T08:32:21Z
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 Thu, 2010-12-23 at 10:53 +0100, Magnus Hagander wrote: > Here's a patch that changes walsender to require a special privilege > for replication instead of relying on superuser permissions. We > discussed this back before 9.0 was finalized, but IIRC we ran out of > time. The motivation being that you really want to use superuser as > little as possible - and since being a replication slave is a read > only role, it shouldn't require the maximum permission available in > the system. Is backup part of this new privilege, or not? I think if we're going to introduce a new level of privilege, then we should introduce all delegatable privs in one software release. Much better than having someone think up a new delegatable priv each release for next 5 years. Other possible ones include unsafe PL creation, seeing logged SQL etc.. -- Simon Riggs http://www.2ndQuadrant.com/books/ PostgreSQL Development, 24x7 Support, Training and Services