From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, MARK CALLAGHAN <mdcallag(at)gmail(dot)com>, Markus Wanner <markus(at)bluegap(dot)ch>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 15:47:46 |
Message-ID: | 4D837EA2.2070205@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 18.03.2011 16:52, Kevin Grittner wrote:
> 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.
To be clear: other users cannot observe the commit until standby
acknowledges it - unless the master crashes while waiting for the
acknowledgment. If that happens, the commit will be visible to everyone
after recovery.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | MARK CALLAGHAN | 2011-03-18 15:52:18 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
Previous Message | Markus Wanner | 2011-03-18 15:43:38 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
From | Date | Subject | |
---|---|---|---|
Next Message | MARK CALLAGHAN | 2011-03-18 15:52:18 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
Previous Message | Markus Wanner | 2011-03-18 15:43:38 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |