Received: from maia.hub.org (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id CEE3B633117;
	Thu,  1 Apr 2010 15:49: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 81237-01; Thu,  1 Apr 2010 18:49: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 3904F632BF4;
	Thu,  1 Apr 2010 15:49: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 <josh@agliodbs.com>)
	id 1NxPSM-0008AR-4d; Thu, 01 Apr 2010 11:49:32 -0700
Message-ID: <4BB4EAB4.3020904@agliodbs.com>
Date: Thu, 01 Apr 2010 11:49:24 -0700
From: Josh Berkus <josh@agliodbs.com>
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: Robert Haas <robertmhaas@gmail.com>
CC: Kevin Grittner <Kevin.Grittner@wicourts.gov>,
	Tom Lane <tgl@sss.pgh.pa.us>,
	Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>,
	Fujii Masao <masao.fujii@gmail.com>, pgsql-docs@postgresql.org,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Streaming replication document improvements
References: <3f0b79eb1003300152g5327eb47w8f9aecae6002b215@mail.gmail.com>
	<t2m603c8f071003311852x3dd15512uc92e0865ba729548@mail.gmail.com>
	<g2z3f0b79eb1003311858y7f781c7u99e09e32c96aa79b@mail.gmail.com>
	<x2t603c8f071003311900v524ab37x44f9e52a2a69dc33@mail.gmail.com>
	<o2u3f0b79eb1003311914i6c9d896bic3d1b13152c6b0d8@mail.gmail.com>
	<4BB49B0C.1050901@enterprisedb.com>
	<j2t603c8f071004011018tbdcc5d17y1fe17b29ab08703c@mail.gmail.com>
	<19262.1270142946@sss.pgh.pa.us>
	<4BB4952D0200002500030333@gw.wicourts.gov>
	<4BB4DBEF.3010301@agliodbs.com>
	<o2m603c8f071004011058neb6e0ea1r1f5caccbb7c50402@mail.gmail.com>
In-Reply-To: <o2m603c8f071004011058neb6e0ea1r1f5caccbb7c50402@mail.gmail.com>
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/8
X-Sequence-Number: 5407


> The thing is, when dealing with new features, we reduce our overall
> maintenance burden if we get it right the first time.  Obviously it's
> too late for major changes, but minor adjustments to maintain the POLA
> seem like exactly what we SHOULD be doing right now.

Oh, I agree.  Since we have a separate WALSender limit, it seems
counter-intuitive and difficult-to-admin to have the WALSenders also
limited by superuser_connections.  They should be their own separate
connection pool, just like the other "background" processes.

However, if this was somehow infeasible, it wouldn't be hard to
document.  That's all.

-- 
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com