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

Kevin Grittner <kevin.grittner@wicourts.gov>

From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>

To: "Simon Riggs" <simon@2ndQuadrant.com>, "MARK CALLAGHAN" <mdcallag@gmail.com>

Cc: "Markus Wanner" <markus@bluegap.ch>, "Alvaro Herrera" <alvherre@commandprompt.com>, "Andrew Dunstan" <andrew@dunslane.net>, "Heikki Linnakangas" <heikki.linnakangas@enterprisedb.com>, "Aidan Van Dyk" <aidan@highrise.ca>, "pgsql-hackers" <pgsql-hackers@postgresql.org>

Date: 2011-03-18T14:52:13Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Efficient transaction-controlled synchronous replication.
- a8a8a3e09652 9.1.0 cited

Simon Riggs <simon@2ndQuadrant.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