Andrew Dunstan <and...@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
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
