Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 34A511337B50 for ; Sat, 1 Jan 2011 13:04:10 -0400 (AST) 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 40713-06 for ; Sat, 1 Jan 2011 17:04:03 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail149095.authsmtp.com (outmail149095.authsmtp.com [62.13.149.95]) by mail.postgresql.org (Postfix) with ESMTP id A8DC31337B5B for ; Sat, 1 Jan 2011 13:04:02 -0400 (AST) Received: from mail-c194.authsmtp.com (mail-c194.authsmtp.com [62.13.128.121]) by punt7.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id p01H3pqJ051180; Sat, 1 Jan 2011 17:03:51 GMT Received: from [192.168.0.2] ([81.5.146.37]) (authenticated bits=0) by mail.authsmtp.com (8.14.2/8.14.2) with ESMTP id p01H3nBA078837; Sat, 1 Jan 2011 17:03:50 GMT Subject: Re: Sync Rep Design From: Simon Riggs To: Stefan Kaltenbrunner Cc: Dimitri Fontaine , Heikki Linnakangas , greg@2ndQuadrant.com, Josh Berkus , Hannu Krosing , Robert Haas , pgsql-hackers@postgresql.org In-Reply-To: <4D1F5838.8020509@kaltenbrunner.cc> References: <1293729972.1892.23804.camel@ebony> <4D1CC47E.7050207@kaltenbrunner.cc> <1293735853.1892.24886.camel@ebony> <4D1D8B2F.5070001@2ndquadrant.com> <4D1DAB14.5000800@enterprisedb.com> <1293796137.1892.37313.camel@ebony> <4D1DCF5A.7070808@enterprisedb.com> <1293822959.1892.43164.camel@ebony> <4D1F332A.90306@kaltenbrunner.cc> <4D1F5838.8020509@kaltenbrunner.cc> Content-Type: text/plain; charset="UTF-8" Date: Sat, 01 Jan 2011 17:03:48 +0000 Message-ID: <1293901428.1892.60565.camel@ebony> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit X-Server-Quench: 1ae33fcf-15c9-11e0-80b9-0022640b883e X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCdxZQATClZOTQEd DAteCiN5VAwpPBRK HVkIKg5MJUcNSQVJ NksafhtFaARbZ1hf HGQLWlVEUVp7WWB/ bgofZQRDZ1RPWwN0 U09WR1pVCwUmQRwA fh1AIGhycA1Oe3k+ Z0RgVngVXRUvdkUr ERhJFGhVbHphaTUf TUhYJQpJcANIfBlB agJ3XHBYLwdSbGoL PyYYHB0LBgAXEzVT SUk3IEpabUsQHzE6 LxMc X-Authentic-SMTP: 61633235383639.1015: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.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201101/20 X-Sequence-Number: 177857 On Sat, 2011-01-01 at 17:37 +0100, Stefan Kaltenbrunner wrote: > On 01/01/2011 05:28 PM, Dimitri Fontaine wrote: > > Stefan Kaltenbrunner writes: > >> well you keep saying that but to be honest I cannot really even see a > >> usecase for me - what is "only a random one of a set of servers is sync at > >> any time and I don't really know which one". > > > > It looks easy enough to get to know which one it is. Surely the primary > > knows and could update something visible through a system view for > > users? This as been asked for before and I was thinking there was a > > consensus on this. > > well as jeff janes already said - anything that requires the master to > still exist is not useful for a desaster. Nobody has suggested that the master needs to still exist after a disaster. > Consider the now often > mentioned 2 sync standby scenario with one standby in the same location > and one in a secondary location. > If you have a desaster(fire,water,explosion,admin fail,...) at the > primary location and you have no access to either the master or the > standby you will never be sure that the standby on the secondary > location is actually "in sync" - it could be but you will never know if > you lost that 1B$ invoice just commited on the master and the closeby > standby and therefor confirmed to the client... I've never suggested you configure your systems like that. It would of course be stupid. This is not a sensible technical discussion. I'll go back to coding. -- Simon Riggs http://www.2ndQuadrant.com/books/ PostgreSQL Development, 24x7 Support, Training and Services