Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "MARK CALLAGHAN" <mdcallag(at)gmail(dot)com>
Cc: "Markus Wanner" <markus(at)bluegap(dot)ch>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Aidan Van Dyk" <aidan(at)highrise(dot)ca>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Date: 2011-03-18 14:52:13
Message-ID: 4D832B4D020000250003BA98@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:

> In PostgreSQL other users cannot observe the commit until an
> acknowledgement has been received.

Really? I hadn't picked up on that. That makes for a lot of
complication on crash-and-recovery of a master, but if we can pull
it off, that's really cool. If we do that and MySQL doesn't, we
definitely don't want to use the same terminology they do, which
would imply the same behavior.

Apologies for not picking up on that aspect of the implementation.

-Kevin

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Greg Stark 2011-03-18 14:55:56 Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Previous Message Thom Brown 2011-03-18 14:41:51 Re: [COMMITTERS] pgsql: Fix various possible problems with synchronous replication.

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2011-03-18 14:55:56 Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Previous Message hom 2011-03-18 14:44:46 Re: I am confused after reading codes of PostgreSQL three week