Re: Streaming replication as a separate permissions
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-12-23T15:15: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
Magnus Hagander <magnus@hagander.net> writes: > 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. Maybe it needn't require "max" permissions, but one of the motivations for requiring superusernesss was to prevent Joe User from sucking every last byte of data out of your database (and into someplace he could examine it at leisure). This patch opens that barn door wide, because so far as I can see, it allows anybody at all to grant the replication privilege ... or revoke it, thereby breaking your replication setup. I think only superusers should be allowed to change the flag. regards, tom lane