Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 8C97A632467
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri, 23 Jul 2010 12:58:36 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 61076-02
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Fri, 23 Jul 2010 15:58:29 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from serenity.inversion.ee (serenity.inversion.ee [194.204.33.112])
	by mail.postgresql.org (Postfix) with ESMTP id 3CE4162DBEC
	for <pgsql-performance@postgresql.org>;
	Fri, 23 Jul 2010 12:58:29 -0300 (ADT)
Received: by serenity.inversion.ee (Postfix, from userid 108)
	id 69FC7E3444F; Fri, 23 Jul 2010 17:40:09 +0300 (EEST)
Received: from [IPv6:::1] (localhost [127.0.0.1])
	by serenity.inversion.ee (Postfix) with ESMTP id 01F4CE343A0;
	Fri, 23 Jul 2010 17:40:08 +0300 (EEST)
Subject: Re: Pooling in Core WAS: Need help in performance tuning.
From: Hannu Krosing <hannu@krosing.net>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Craig Ringer <craig@postnewspapers.com.au>,
	Matthew Wakeling <matthew@flymine.org>, pgsql-performance@postgresql.org
In-Reply-To: <AANLkTimLr9AoMMB_k9GWuEgoBZg1YWxR5OqKY-1Ugimc@mail.gmail.com>
References: <AANLkTiknhZhKtGDidBsMWtPJpRgln9DrrsCebCEYk5XE@mail.gmail.com>
	<4C369346.6010501@postnewspapers.com.au>
	<AANLkTin4Q4APRnbJ85FRasU7n8LuhKibKYcGnexsEbTt@mail.gmail.com>
	<8760.1278650566@sss.pgh.pa.us>
	<1278680186.1914.36.camel@bnicholson-desktop>
	<4C36F57102000025000332F6@gw.wicourts.gov>
	<alpine.DEB.2.00.1007091621380.2534@aragorn.flymine.org>
	<4C36FEAD02000025000332FC@gw.wicourts.gov>
	<alpine.DEB.2.00.1007091753350.2534@aragorn.flymine.org>
	<4C37A9C1.1060405@2ndquadrant.com>
	<4C37791C0200002500033379@gw.wicourts.gov>
	<4C37CBFB.1000800@agliodbs.com>
	<4C37EA1D.6000008@postnewspapers.com.au>
	<AANLkTimNJZlX7kFH_r0-BB_K3NGorU7BHd85SxXJbuGJ@mail.gmail.com>
	<4C38BF03.6060503@agliodbs.com> <19244.1278787866@sss.pgh.pa.us>
	<alpine.DEB.2.00.1007121044330.2534@aragorn.flymine.org>
	<4C3AF564.5030204@postnewspapers.com.au>
	<AANLkTinDgkzqf_=O+hk5OMq+AxN4G+fpfQZM4DBizAOF@mail.gmail.com>
	<1279826144.14271.5.camel@hvost>
	<AANLkTimLr9AoMMB_k9GWuEgoBZg1YWxR5OqKY-1Ugimc@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 23 Jul 2010 16:58:27 +0100
Message-ID: <1279900707.26952.4.camel@hvost>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.1 
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9
X-Spam-Level: 
X-Archive-Number: 201007/338
X-Sequence-Number: 39727

On Thu, 2010-07-22 at 20:57 -0400, Robert Haas wrote:
> On Thu, Jul 22, 2010 at 3:15 PM, Hannu Krosing <hannu@krosing.net> wrote:
> > On Thu, 2010-07-22 at 14:36 -0400, Robert Haas wrote:
> >> On Mon, Jul 12, 2010 at 6:58 AM, Craig Ringer
> >> <craig@postnewspapers.com.au> wrote:
> >> > So rather than asking "should core have a connection pool" perhaps
> >> > what's needed is to ask "what can an in-core pool do that an external
> >> > pool cannot do?"
> >>
> >> Avoid sending every connection through an extra hop.
> >
> > not really. in-core != magically-in-right-backend-process
> 
> Well, how about if we arrange it so it IS in the right backend
> process?  I don't believe magic is required.

Do you have any design in mind, how you can make it so ?

---------------
Hannu