Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 1663B6357AC;
	Tue, 20 Apr 2010 11:46:55 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024)
	with ESMTP id 23832-02-2; Tue, 20 Apr 2010 14:46:33 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 71B9F636085;
	Tue, 20 Apr 2010 11:08:57 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o3KE8b91026450;
	Tue, 20 Apr 2010 10:08:37 -0400 (EDT)
To: Robert Haas <robertmhaas@gmail.com>
cc: Fujii Masao <masao.fujii@gmail.com>, Josh Berkus <josh@agliodbs.com>,
	Kevin Grittner <Kevin.Grittner@wicourts.gov>,
	Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>,
	pgsql-docs@postgresql.org,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Streaming replication document improvements 
In-reply-to: <h2g603c8f071004200701jff98aca6sfd063608572e463@mail.gmail.com> 
References: <3f0b79eb1003300152g5327eb47w8f9aecae6002b215@mail.gmail.com>
	<19262.1270142946@sss.pgh.pa.us>
	<4BB4952D0200002500030333@gw.wicourts.gov>
	<4BB4DBEF.3010301@agliodbs.com>
	<o2m603c8f071004011058neb6e0ea1r1f5caccbb7c50402@mail.gmail.com>
	<k2i3f0b79eb1004012306xdfa88c1cudd77b61368c997ea@mail.gmail.com>
	<w2z603c8f071004191904yefcaba2fy1abc2020174a35c5@mail.gmail.com>
	<s2u3f0b79eb1004200247q2f1c35f0pc7bf4af306f3514c@mail.gmail.com>
	<j2r603c8f071004200352s5e175371z8bd42b9c18807fe@mail.gmail.com>
	<h2w3f0b79eb1004200647nc0aa56d8ibb4be9f2f00731f5@mail.gmail.com>
	<h2g603c8f071004200701jff98aca6sfd063608572e463@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Tue, 20 Apr 2010 10:01:48 -0400"
Date: Tue, 20 Apr 2010 10:08:37 -0400
Message-ID: <26449.1271772517@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.046 tagged_above=-10 required=5 tests=AWL=-2.363,
	BAYES_00=-1.9, FS_REPLICA=3.599, SARE_SPEC_REPLICA=0.72,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201004/69
X-Sequence-Number: 5468

Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Apr 20, 2010 at 9:47 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
>> 3. Your proposal
>>    Treat superuser replication connection like non-superuser one

> Well, only for this one very specific purpose.  I would adjust the
> docs like this:

> Determines the number of connection "slots" that are reserved for
> connections by PostgreSQL  superusers. At most max_connections
> connections can ever be active simultaneously. Whenever the number of
> active concurrent connections is at least max_connections minus
> superuser_reserved_connections, new connections will be accepted only
> for superusers, and no new replication connections will be accepted.

> I think that's pretty simple and clear.

+1.  I'm not sure about the consequences of converting walsender to
non-superuser across the board, and would prefer not to experiment
with it at this stage of the release cycle.

			regards, tom lane