From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Andrew Dunstan <andrew@dunslane.net>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Date: Mon, 07 Mar 2011 09:13:46 -0600
Message-ID: <4D74A1CA020000250003B569@gw.wicourts.gov> (raw)
In-Reply-To: <4D74F3AE.9000802@dunslane.net>
References: <E1PwMns-00047O-UU@gemulon.postgresql.org>
<4D741441.2090704@dunslane.net>
<1299454125.1696.6138.camel@ebony>
<4D74896C.5030402@enterprisedb.com>
<4D74DDFA.70800@dunslane.net>
<4D74E584.7080409@enterprisedb.com>
<4D74E9FA.7070202@dunslane.net>
<AANLkTinkzJ=UrLbThZy2KeQg+SjwYqj2r0mDomMwirB7@mail.gmail.com>
<4D74F3AE.9000802@dunslane.net>
Andrew Dunstan <andrew@dunslane.net> wrote:
> Synchronous replication - guarantees "zero data loss" by the
> means of atomic write operation, i.e. write either completes on
> both sides or not at all.
So far, so good.
> Write is not considered complete until acknowledgement by both
> local and remote storage.
OK, *if* we want to live up to this definition, we don't seem to
have that part covered. Of course, since the connection is broken
during the hypothetical crash, it seems hard to acknowledge it on
recovery, and short of 2PC I don't see how we roll it back. About
the best we could do is somehow have explicit logging of the
disposition of unacknowledged commit requests upon recovery, and
consider logging of success to be "acknowledgement". Is this
logging provided by other databases with "synchronous replication"
features?
-Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, andrew@dunslane.net, aidan@highrise.ca, simon@2ndquadrant.com, heikki.linnakangas@enterprisedb.com, pgsql-hackers@postgresql.org
Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
In-Reply-To: <4D74A1CA020000250003B569@gw.wicourts.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox