Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id DE8126327E1; Thu, 1 Apr 2010 14:46:50 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 70537-03; Thu, 1 Apr 2010 17:46:40 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from glacier.frostconsultingllc.com (glacier.frostconsultingllc.com [69.36.227.170]) by mail.postgresql.org (Postfix) with ESMTP id 5E2D76325B4; Thu, 1 Apr 2010 14:46:40 -0300 (ADT) Received: from dsl081-245-111.sfo1.dsl.speakeasy.net ([64.81.245.111] helo=Sidney-Stratton.local) by glacier.frostconsultingllc.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.69) (envelope-from ) id 1NxOTN-0007si-6e; Thu, 01 Apr 2010 10:46:31 -0700 Message-ID: <4BB4DBEF.3010301@agliodbs.com> Date: Thu, 01 Apr 2010 10:46:23 -0700 From: Josh Berkus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: Kevin Grittner CC: Robert Haas , Tom Lane , Heikki Linnakangas , Fujii Masao , pgsql-docs@postgresql.org, PostgreSQL-development Subject: Re: [HACKERS] Streaming replication document improvements References: <3f0b79eb1003300152g5327eb47w8f9aecae6002b215@mail.gmail.com> <4BB3B2ED.5080606@enterprisedb.com> <4BB49B0C.1050901@enterprisedb.com> <19262.1270142946@sss.pgh.pa.us> <4BB4952D0200002500030333@gw.wicourts.gov> In-Reply-To: <4BB4952D0200002500030333@gw.wicourts.gov> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.838 tagged_above=-10 required=5 tests=BAYES_00=-2.599, FS_REPLICA=1.041, SARE_SPEC_REPLICA=0.72 X-Spam-Level: X-Archive-Number: 201004/7 X-Sequence-Number: 5406 On 4/1/10 10:44 AM, Kevin Grittner wrote: > It seems within the realm of possibility that not all users would > think to boost superuser_reserved_connections by the number of > replication connections, and be surprised when they are unable to > connect in an emergency. Well, that's easy to add to the documentation. -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com