Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id A218E632868 for ; Sat, 24 Jul 2010 02:23:22 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 26792-05 for ; Sat, 24 Jul 2010 05:23:15 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mail.postgresql.org (Postfix) with ESMTP id 23EC76324AA for ; Sat, 24 Jul 2010 02:23:15 -0300 (ADT) Received: from [192.168.1.5] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MNO5B-1Oez6V13P7-006cJG; Sat, 24 Jul 2010 07:23:11 +0200 Message-ID: <4C4A78BC.2020101@2ndquadrant.com> Date: Sat, 24 Jul 2010 01:23:08 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Joshua Tolley CC: Scott Carey , Robert Haas , Craig Ringer , Matthew Wakeling , "pgsql-performance@postgresql.org" Subject: Re: Pooling in Core WAS: Need help in performance tuning. References: <4C37791C0200002500033379@gw.wicourts.gov> <4C37CBFB.1000800@agliodbs.com> <4C37EA1D.6000008@postnewspapers.com.au> <4C38BF03.6060503@agliodbs.com> <19244.1278787866@sss.pgh.pa.us> <4C3AF564.5030204@postnewspapers.com.au> <82DAA0BC-52E8-4279-81DF-14373755A42F@richrelevance.com> <4c49bb81.17bb720a.42c2.1de8@mx.google.com> In-Reply-To: <4c49bb81.17bb720a.42c2.1de8@mx.google.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:QaYBQQyw/tHj4MkzbM+z+orRdHm3r1jQe3TS9ombk2G j35QlUuzpAP6pj10SnXHKMnKr4n4eL1G9hgVJOXLUfGhdZ8iCM SquDOzOyAvtmtxYpZ0JMiQyqDL7VEZwJ+Xm3HtDq6O/LSiB/Ab 6VvyuzQ1c0CNVguUfV5YD8lRNbVLk3JdMvGJP+C0b6smQ0bqxS EZ9zWEwCgpYWwaRcJ0oGCerLZknU+gPudqV3rjxADk= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.5 tagged_above=-10 required=5 tests=BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201007/345 X-Sequence-Number: 39734 Joshua Tolley wrote: > Relatively minor, but it would be convenient to avoid having to query > $external_pooler to determine the client_addr of an incoming connection. > You suggest this as a minor concern, but I consider it to be one of the most compelling arguments in favor of in-core pooling. A constant pain with external poolers is the need to then combine two sources of data in order to track connections fully, which is something that everyone runs into eventually and finds annoying. It's one of the few things that doesn't go away no matter how much fiddling you do with pgBouncer, it's always getting in the way a bit. And it seems to seriously bother systems administrators and developers, not just the DBAs. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us