Re: Issues with Quorum Commit - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Issues with Quorum Commit
Date
Msg-id 1286526301.2304.537.camel@ebony
Whole thread Raw
In response to Re: Issues with Quorum Commit  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Issues with Quorum Commit
List pgsql-hackers
On Fri, 2010-10-08 at 10:56 +0300, Heikki Linnakangas wrote:
> >
> > Or what kind of customers do you think really need a no-lag solution for
> > read-only queries? In the LAN case, the lag of async rep is negligible
> > and in the WAN case the latencies of sync rep are prohibitive.
> 
> There is a very good use case for that particular set up, actually. If 
> your hot standby is guaranteed to be up-to-date with any transaction 
> that has been committed in the master, you can use the standby 
> interchangeably with the master for read-only queries. 

This is an important point. It is desirable, but there is no such thing.
We must not take any project decisions based upon that false premise.

Hot Standby is never guaranteed to be up-to-date with master. There is
no such thing as certainty that you have the same data as the master.

All sync rep gives you is a better durability guarantee that the changes
are safe. It doesn't guarantee those changes are transferred to all
nodes prior to making the data changes on any one standby.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Development, 24x7 Support, Training and Services



pgsql-hackers by date:

Previous
From: Leonardo Francalanci
Date:
Subject: Re: I: About "Our CLUSTER implementation is pessimal" patch
Next
From: Yeb Havinga
Date:
Subject: Re: standby registration (was: is sync rep stalled?)