Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 382CD6335FA;
	Thu,  1 Apr 2010 11:09:08 -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 48016-03; Thu,  1 Apr 2010 14:08:48 +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 462DC63356E;
	Thu,  1 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 o31E8nRX015382;
	Thu, 1 Apr 2010 10:08:49 -0400 (EDT)
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
cc: Fujii Masao <masao.fujii@gmail.com>, Robert Haas <robertmhaas@gmail.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	pgsql-docs@postgresql.org
Subject: Re: [HACKERS] Streaming replication document improvements 
In-reply-to: <4BB49B0C.1050901@enterprisedb.com> 
References: <3f0b79eb1003300152g5327eb47w8f9aecae6002b215@mail.gmail.com>
	<4BB3B2ED.5080606@enterprisedb.com>
	<u2w3f0b79eb1003311850m50193801tb49b04966f5544d0@mail.gmail.com>
	<t2m603c8f071003311852x3dd15512uc92e0865ba729548@mail.gmail.com>
	<g2z3f0b79eb1003311858y7f781c7u99e09e32c96aa79b@mail.gmail.com>
	<x2t603c8f071003311900v524ab37x44f9e52a2a69dc33@mail.gmail.com>
	<o2u3f0b79eb1003311914i6c9d896bic3d1b13152c6b0d8@mail.gmail.com>
	<4BB49B0C.1050901@enterprisedb.com>
Comments: In-reply-to Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
	message dated "Thu, 01 Apr 2010 16:09:32 +0300"
Date: Thu, 01 Apr 2010 10:08:49 -0400
Message-ID: <15381.1270130929@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=-1.584 tagged_above=-10 required=5 tests=AWL=-0.746,
	BAYES_00=-2.599, FS_REPLICA=1.041, SARE_SPEC_REPLICA=0.72
X-Spam-Level: 
X-Archive-Number: 201004/5
X-Sequence-Number: 5404

Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Fujii Masao wrote:
>> Preventing superuser connections from consuming superuser_reserved_connections
>> slots seems strange for me. So I'm leaning toward just removing superuser
>> privilege from replication connection again. Thought?

> That would be good, but I fear it's a bigger change than we should be
> doing at this point.

Exactly.  Despite Robert's unhappiness, NONE of this should get changed
right now.  When and if we create a separate replication privilege,
it'll be time enough to revisit the connection limit arithmetic.

			regards, tom lane