| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "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>, "MARK CALLAGHAN" <mdcallag(at)gmail(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 21:48:33 |
| Message-ID: | 4D838CE1020000250003BB06@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-03-18 22:41:35 | pgsql: Document the all-balls IPv6 address. |
| Previous Message | Robert Haas | 2011-03-18 21:43:32 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-03-18 21:57:32 | Re: SSI bug? |
| Previous Message | Robert Haas | 2011-03-18 21:43:32 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |