Horton

Re: Configuring synchronous replication

Dimitri Fontaine <dfontaine@hi-media.com>

View thread
From: Dimitri Fontaine <dfontaine@hi-media.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, 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>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Fujii Masao <masao.fujii@gmail.com>, Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org
Date: 2010-09-24T11:05:25Z
Lists: pgsql-hackers 
Robert Haas <robertmhaas@gmail.com> writes:
> I think maybe you missed Tom's point, or else you just didn't respond
> to it.  If the master is wedged because it is waiting for a standby,
> then you cannot commit transactions on the master.  Therefore you
> cannot update the system catalog which you must update to unwedge it.
> Failing over in that situation is potentially a huge nuisance and
> extremely undesirable.

All Wrong.

You might remember that Simon's proposal begins with per-transaction
synchronous replication behavior?

Regards,
-- 
dim