Horton

Re: Configuring synchronous replication

Simon Riggs <simon@2ndquadrant.com>

View thread
From: Simon Riggs <simon@2ndQuadrant.com>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, jd@commandprompt.com, Thom Brown <thom@linux.com>, Bruce Momjian <bruce@momjian.us>, Andrew Dunstan <andrew@dunslane.net>, Dave Page <dpage@pgadmin.org>, Peter Eisentraut <peter_e@gmx.net>, Fujii Masao <masao.fujii@gmail.com>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2010-09-24T10:59:42Z
Lists: pgsql-hackers 
On Fri, 2010-09-24 at 11:43 +0300, Heikki Linnakangas wrote:
> > To get zero data loss *and* continuous availability, you need two
> > standbys offering sync rep and reply-to-first behaviour.
> 
> Yes, that is a good point.
> 
> I'm starting to understand what your proposal was all about. It makes 
> sense when you think of a three node system configured for high 
> availability with zero data loss like that.
> 
> The use case of keeping hot standby servers up todate in a cluster
> where 
> read-only queries are distributed across all nodes seems equally 
> important though. What's the simplest method of configuration that 
> supports both use cases?

That is definitely the right question. (More later)

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