From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Simon Riggs" <simon(at)2ndQuadrant(dot)com>, "Markus Wanner" <markus(at)bluegap(dot)ch> |
Cc: | "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 19:34:18 |
Message-ID: | 4D836D6A020000250003BAE4@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:
> On Fri, 2011-03-18 at 20:19 +0100, Markus Wanner wrote:
>> >>> Simon Riggs<simon(at)2ndQuadrant(dot)com> wrote:
>> >>>> In PostgreSQL other users cannot observe the commit until an
>> >>>> acknowledgement has been received.
>>
>> On other nodes as well? To me that means the standby needs to
>> hold back COMMIT of an ACKed transaction, until receives a re-ACK
>> from the master, that it committed the transaction there. How
>> else could the slave know when to commit its ACKed transactions?
>
> We could do that easily enough, actually, if we wished.
>
> Do we wish?
+1
If we're going out of our way to suppress it on the master until the
COMMIT returns, it shouldn't be showing on the replicas before that.
-Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Wanner | 2011-03-18 19:41:00 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
Previous Message | Simon Riggs | 2011-03-18 19:29:50 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Wanner | 2011-03-18 19:41:00 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
Previous Message | Simon Riggs | 2011-03-18 19:29:50 | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |