Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 811366337E0;
	Wed, 31 Mar 2010 22:58:18 -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 70455-01; Thu,  1 Apr 2010 01:58:07 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-gx0-f223.google.com (mail-gx0-f223.google.com
	[209.85.217.223])
	by mail.postgresql.org (Postfix) with ESMTP id CFDD163357D;
	Wed, 31 Mar 2010 22:58:07 -0300 (ADT)
Received: by gxk23 with SMTP id 23so573546gxk.15
	for <multiple recipients>; Wed, 31 Mar 2010 18:58:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:received:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=es7UznyhTifOUW89MhT3qOfKQT4NET/axFmOkriP6G4=;
	b=nKQVyJfHfNtdtJw1ZIClt6fQI7F00+9/gL4YszC4V8LaA2BNkA5hIchlHSAAnCl58h
	Qv1IgacrKX2rVL7Ne9tgCYTQI2EUDR0m4MQALvwrEQMnPChs4pcfvQds81oCtOyMy00l
	ej4l1wycYtjDoG0VWsPQHcNXkQa8w8cs1dX/Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=jHzPh6g3Br31Jl2t4z99+sLL0tlS28jhejUTtFvuJDCyRu81tfUrpFPZLZLPk8mC2T
	IQFZg6sSajUOqBA5VOGwzzmUuVGI1DjsTjyTaYOI1QZ5Nw8b2a3+ZpU2wM/I+VBsawnB
	coEjjapv93UdHO5atS9f1kK8bfydp4Gu24FOU=
MIME-Version: 1.0
Received: by 10.100.253.9 with HTTP; Wed, 31 Mar 2010 18:58:05 -0700 (PDT)
In-Reply-To: <t2m603c8f071003311852x3dd15512uc92e0865ba729548@mail.gmail.com>
References: <3f0b79eb1003300152g5327eb47w8f9aecae6002b215@mail.gmail.com>
	<4BB3B2ED.5080606@enterprisedb.com>
	<u2w3f0b79eb1003311850m50193801tb49b04966f5544d0@mail.gmail.com>
	<t2m603c8f071003311852x3dd15512uc92e0865ba729548@mail.gmail.com>
Date: Thu, 1 Apr 2010 10:58:05 +0900
Received: by 10.100.129.6 with SMTP id b6mr1136231and.90.1270087085966; Wed,
	31 Mar 2010 18:58:05 -0700 (PDT)
Message-ID: <g2z3f0b79eb1003311858y7f781c7u99e09e32c96aa79b@mail.gmail.com>
Subject: Re: [HACKERS] Streaming replication document improvements
From: Fujii Masao <masao.fujii@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	pgsql-docs@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: 201003/33
X-Sequence-Number: 5398

On Thu, Apr 1, 2010 at 10:52 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Wed, Mar 31, 2010 at 9:50 PM, Fujii Masao <masao.fujii@gmail.com> wrot=
e:
>>> That's an interesting point, do streaming replication connections
>>> consume superuser_reserved_connections slots?
>>
>> Yes. Since SR connection is superuser connection, setting
>> superuser_reserved_connections appropriately would be useful
>> to prevent non-superuser connections from blocking the connection
>> from the standby.
>
> I think this is wacky, especially since we'd someday like to have
> replication be a separate privilege from superuser. =A0I think we should
> change this.

You mean that we should change replication connection not to consume
superuser_reserved_connections slots in 9.0?

Regards,

--=20
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center