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

Kevin Grittner <kevin.grittner@wicourts.gov>

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

To: "Robert Haas" <robertmhaas@gmail.com>

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

Date: 2011-03-18T21:48:33Z

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

Robert Haas <robertmhaas@gmail.com> wrote:

> Well, the idea is that we don't want to let people depend on the
> value until it's guaranteed to be durably committed.

OK, so if you see it on the replica, you know it is in at least two
places.  I guess that makes sense.  It kinda "feels" wrong to see a
view of the replica which is ahead of the master, but I guess it's
the least of the evils.  I guess we should document it, though, so
nobody has a false expectation that seeing something on the replica
means that a connection looking at the master will see something
that current.

-Kevin