Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id CF5A01337B77 for ; Tue, 4 Jan 2011 18:01:14 -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 24518-06; Tue, 4 Jan 2011 22:01:07 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from acidenitrix.villemain.org (acidenitrix.villemain.org [91.121.90.165]) by mail.postgresql.org (Postfix) with ESMTP id 2CA441337B5C; Tue, 4 Jan 2011 18:01:07 -0400 (AST) Received: from 89-158-241-48.rev.dartybox.com ([89.158.241.48] helo=DimIMac.local) by acidenitrix.villemain.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1PaEw8-0007xs-9a; Tue, 04 Jan 2011 23:01:00 +0100 Received: by DimIMac.local (Postfix, from userid 501) id 3AE69163E0BA; Tue, 4 Jan 2011 23:00:54 +0100 (CET) From: Dimitri Fontaine To: Josh Berkus Cc: Heikki Linnakangas , Stefan Kaltenbrunner , Simon Riggs , greg@2ndQuadrant.com, Hannu Krosing , Robert Haas , pgsql-hackers@postgresql.org Subject: Re: Sync Rep Design Organization: 2ndQuadrant 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> <4D1FAD55.1090304@postgresql.org> <4D2038BB.7000504@enterprisedb.com> <4D236999.4050905@postgresql.org> User-Mail-Address: dimitri@2ndQuadrant.fr Date: Tue, 04 Jan 2011 23:00:53 +0100 In-Reply-To: <4D236999.4050905@postgresql.org> (Josh Berkus's message of "Tue, 04 Jan 2011 10:40:25 -0800") Message-ID: User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (darwin) MIME-Version: 1.0 Content-Type: text/plain 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/286 X-Sequence-Number: 178123 Josh Berkus writes: > So, again, I don't agree that a separate synchrep permission is useful, > or warranted. +1 > However, your arguments *do* make me backpedal on the issue of having a > list of synch rep roles on the master. I can easily imagine a DBA > needing to rapidly disable synch rep if replication is failing, without > taking the time to log in to several separate standbys, one or more of > which might be improperly configured and inaccessible. I can't think of > a simpler way to do that than having a synch_rep_roles configuration on > the master. That would also handle control issues for the senior DBA, > since you'd need superuser access to the master to modify it. What about the HBA here? Regards, -- Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support