Horton

Re: Sync Rep Design

Dimitri Fontaine <dimitri@2ndquadrant.fr>

View thread
From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
To: Josh Berkus <josh@postgresql.org>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>, Simon Riggs <simon@2ndQuadrant.com>, greg@2ndQuadrant.com, Hannu Krosing <hannu@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org
Date: 2011-01-04T22:00:53Z
Lists: pgsql-hackers 
Josh Berkus <josh@postgresql.org> writes:
> So, again, I don't agree that a separate synchrep permission is useful,
> or warranted.

+1

> However, your arguments *do* make me backpedal on the issue of having a
> list of synch rep roles on the master.  I can easily imagine a DBA
> needing to rapidly disable synch rep if replication is failing, without
> taking the time to log in to several separate standbys, one or more of
> which might be improperly configured and inaccessible.  I can't think of
> a simpler way to do that than having a synch_rep_roles configuration on
> the master.  That would also handle control issues for the senior DBA,
> since you'd need superuser access to the master to modify it.

What about the HBA here?

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support