Re: Sync Rep Design - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Sync Rep Design
Date
Msg-id m2sjx8l46i.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: Sync Rep Design  (Josh Berkus <josh@postgresql.org>)
Responses Re: Sync Rep Design  (Josh Berkus <josh@postgresql.org>)
List 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


pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: Re: Vacuum of newly activated 8.3.12 standby receives warnings page xxx is uninitialized --- fixing
Next
From: Josh Berkus
Date:
Subject: Re: Sync Rep Design