On Tue, May 25, 2010 at 6:28 PM, Simon Riggs <si...@2ndquadrant.com> wrote: ....... > > The best parameter we can specify is the number of servers that we wish > to wait for confirmation from. That is a definition that easily manages > the complexity of having various servers up/down at any one time. It > also survives misconfiguration more easily, as well as providing a > workaround if replicating across a bursty network where we can't > guarantee response times, even of the typical response time is good. >
This may be an incredibly naive question, but what happens to the transaction on the master if the number of confirmations is not received? Is this intended to create a situation where the master effectively becomes unavailable for write operations when its synchronous slaves are unavailable? Alastair "Bell" Turner ^F5 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
