Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 2A15E1337B81 for ; Fri, 18 Mar 2011 13:19:58 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 74674-07 for ; Fri, 18 Mar 2011 16:19:50 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail148113.authsmtp.com (outmail148113.authsmtp.com [62.13.148.113]) by mail.postgresql.org (Postfix) with ESMTP id 72837133655C for ; Fri, 18 Mar 2011 13:19:50 -0300 (ADT) Received: from mail-c193.authsmtp.com (mail-c193.authsmtp.com [62.13.128.118]) by punt10.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id p2IGJZ54001992; Fri, 18 Mar 2011 16:19:35 GMT Received: from [192.168.0.3] ([81.5.146.37]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2) with ESMTP id p2IGJW34055099; Fri, 18 Mar 2011 16:19:32 GMT Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. From: Simon Riggs To: Heikki Linnakangas Cc: Kevin Grittner , MARK CALLAGHAN , Markus Wanner , Alvaro Herrera , Andrew Dunstan , Aidan Van Dyk , pgsql-hackers In-Reply-To: <4D837EA2.2070205@enterprisedb.com> References: <4D741441.2090704@dunslane.net> <1299454125.1696.6138.camel@ebony> <4D74896C.5030402@enterprisedb.com> <4D74DDFA.70800@dunslane.net> <4D74E584.7080409@enterprisedb.com> <4D74E9FA.7070202@dunslane.net> <4D74F3AE.9000802@dunslane.net> <4D74FDEC.5040406@enterprisedb.com> <4D74FF15.1070804@dunslane.net> <1299513979-sup-1987@alvh.no-ip.org> <4D832571.5030808@bluegap.ch> <1300457958.18619.13780.camel@ebony> <4D832B4D020000250003BA98@gw.wicourts.gov> <4D837EA2.2070205@enterprisedb.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 18 Mar 2011 16:19:31 +0000 Message-ID: <1300465171.18619.15193.camel@ebony> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit X-Server-Quench: 82241a31-517b-11e0-97bb-002264978518 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCdxZQATClZOTQEd DAteCiN5VAwpPBRK HVkIKg5MJUcNSQVJ NksafhtFaQ1bYFhD HGQLWlVEUVt7WGp/ aAgfZQRDZ1RPWwN0 U09WR1pVCwUmQR54 cWR5UR1ycgBGcXc+ Z0djWnQVVEZ4cUcs QU9JEGwBN3phaTUf TUlfJVFJcANIfBlB Y1d3UXIFLwdSbGoL PyYYHB0LBgAXEikH CjImCnc3YHo3MwQH clgaEi42GR9Nais9 LhcnJ1gAfg4NKEw0 KlIqRVMfNVoZDQtC BUZJBCJVb0IQQSEr FwRcWlMFWCdQWSNd CRQ0IxhORFQA X-Authentic-SMTP: 61633235383639.1014:706 X-AuthFastPath: 0 (Was 255) X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.719 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FS_REPLICA=3.599, RCVD_IN_DNSWL_LOW=-0.7, SARE_SPEC_REPLICA=0.72 X-Spam-Level: * X-Archive-Number: 201103/1145 X-Sequence-Number: 184395 On Fri, 2011-03-18 at 17:47 +0200, Heikki Linnakangas wrote: > On 18.03.2011 16:52, Kevin Grittner wrote: > > Simon Riggs 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. No, only in the case where you choose not to failover to the standby when you crash, which would be a fairly strange choice after the effort to set up the standby. In a correctly configured and operated cluster what I say above is fully correct and needs no addendum. -- Simon Riggs http://www.2ndQuadrant.com/books/ PostgreSQL Development, 24x7 Support, Training and Services