Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id C0D361337B9A for ; Sat, 1 Jan 2011 18:41:28 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 52537-05; Sat, 1 Jan 2011 22:41:22 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from outmail148106.authsmtp.co.uk (outmail148106.authsmtp.co.uk [62.13.148.106]) by mail.postgresql.org (Postfix) with ESMTP id 47DC41337B99; Sat, 1 Jan 2011 18:41:21 -0400 (AST) Received: from mail-c194.authsmtp.com (mail-c194.authsmtp.com [62.13.128.121]) by punt3.authsmtp.com (8.14.2/8.14.2/Kp) with ESMTP id p01MfCoj050753; Sat, 1 Jan 2011 22:41:12 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 p01MfBhu025737; Sat, 1 Jan 2011 22:41:11 GMT Subject: Re: Sync Rep Design From: Simon Riggs To: Heikki Linnakangas Cc: Hannu Krosing , greg@2ndQuadrant.com, Josh Berkus , Robert Haas , Stefan Kaltenbrunner , pgsql-hackers@postgresql.org In-Reply-To: <4D1F8383.8020809@enterprisedb.com> 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> <4D1E4897.1050400@2ndquadrant.com> <4D1F8383.8020809@enterprisedb.com> Content-Type: text/plain; charset="UTF-8" Date: Sat, 01 Jan 2011 22:41:10 +0000 Message-ID: <1293921670.1892.65467.camel@ebony> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit X-Server-Quench: 3b973b64-15f8-11e0-80b9-0022640b883e X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCdxZQATClZOTQEd DAteCiN5VAwpPBRK HVkIKg5MJUcNSQVJ NksacRtFaARbZ1hf HGQLWlVEUl97XWJ/ agsfZQRDZ1RPWwN0 U09WR1pVCwUmQRwA e0hsClxydQBBe3k+ ZEVrWnQVXxZzckUv REpJFGhQbXphaTUf TUhYJQpJcANIfBlB agJ3XHBYLwdSbGoL PyYYHB0LBgAXEzVT SUk3IEpabUsQHzE6 L9OX X-Authentic-SMTP: 61633235383639.1015:706 X-AuthFastPath: 255 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 X-Spam-Level: X-Archive-Number: 201101/42 X-Sequence-Number: 177879 On Sat, 2011-01-01 at 21:41 +0200, Heikki Linnakangas wrote: > On 31.12.2010 23:18, Hannu Krosing wrote: > > On 31.12.2010 13:40, Heikki Linnakangas wrote: > >> That thread makes no mention of how to specify which standbys are > >> synchronous and which are not. > > The simplest way would be to have separate database users for sync and > > async standbys ? > > > > That would allow any standby with right credentials act as a sync user, > > and those who are not eligible are not accepted even if they try to act > > as "a synchronity (?) provider". > > Hmm, access control... We haven't yet discussed what privileges a > standby needs to become synchronous. Perhaps it needs to be a separate > privilege that can be granted, in addition to the replication privilege? Perhaps we don't need it, also. Why is that essential in this release? -- Simon Riggs http://www.2ndQuadrant.com/books/ PostgreSQL Development, 24x7 Support, Training and Services