Re: Synchronization levels in SR - Mailing list pgsql-hackers

From Alastair Turner
Subject Re: Synchronization levels in SR
Date
Msg-id AANLkTilm-stWmjVMHqE4KHu6ttHslVTOe_6-gxqDfUo1@mail.gmail.com
Whole thread Raw
In response to Re: Synchronization levels in SR  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Tue, May 25, 2010 at 6:28 PM, Simon Riggs <simon@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


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Synchronization levels in SR
Next
From: Andrew Dunstan
Date:
Subject: Re: [PATCH] Add XMLEXISTS function from the SQL/XML standard