Re: standby registration (was: is sync rep stalled?) - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: standby registration (was: is sync rep stalled?)
Date
Msg-id 4CAE0739.9030904@agliodbs.com
Whole thread Raw
In response to Re: standby registration (was: is sync rep stalled?)  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: standby registration (was: is sync rep stalled?)
List pgsql-hackers
On 10/7/10 10:27 AM, Heikki Linnakangas wrote:
> The standby name is a GUC in the standby's configuration file:
> 
> standby_name='bostonserver'
> 
> The list of important nodes is also a GUC, in the master's configuration
> file:
> 
> synchronous_standbys='bostonserver, oxfordserver'

This seems to abandon Simon's concept of per-transaction synchronization
control.  That seems like such a potentially useful feature that I'm
reluctant to abandon it just for administrative elegance.

Does this work together with that in some way I can't see?

--                                  -- Josh Berkus                                    PostgreSQL Experts Inc.
                        http://www.pgexperts.com
 


pgsql-hackers by date:

Previous
From: Aidan Van Dyk
Date:
Subject: Re: Issues with Quorum Commit
Next
From: Josh Berkus
Date:
Subject: Re: Issues with Quorum Commit