Re: Configuring synchronous replication - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Configuring synchronous replication
Date
Msg-id AANLkTimbd6ExgLX5k1MZrMFKoVUep1ccBUUxQPB4h=ch@mail.gmail.com
Whole thread Raw
In response to Configuring synchronous replication  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Configuring synchronous replication
Re: Configuring synchronous replication
List pgsql-hackers
On Fri, Sep 17, 2010 at 5:09 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> * Quorum commit. Wait until n standbys acknowledge. n=1 and n=all servers
> can be seen as important special cases of this.

I think that we should skip quorum commit at the first phase
because the design seems to be still poorly-thought-out.

I'm concerned about the case where the faster synchronous standby
goes down and the lagged synchronous one remains when n=1. In this
case, some transactions marked as committed in a client might not
be replicated to the remaining synchronous standby yet. What if
the master goes down at this point? How can we determine whether
promoting the remaining standby to the master causes data loss?

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Configuring synchronous replication
Next
From: Robert Haas
Date:
Subject: Re: Configuring synchronous replication