Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 3B8A9632FB0 for ; Thu, 29 Jul 2010 14:39:31 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 55281-01 for ; Thu, 29 Jul 2010 17:39:23 +0000 (UTC) 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 8F5D3632E0E for ; Thu, 29 Jul 2010 14:39:23 -0300 (ADT) Received: from dsl081-245-111.sfo1.dsl.speakeasy.net ([64.81.245.111] helo=[192.168.1.118]) by glacier.frostconsultingllc.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.69) (envelope-from ) id 1OeX4e-0000OL-Gn for pgsql-performance@postgresql.org; Thu, 29 Jul 2010 10:39:19 -0700 Message-ID: <4C51BCC2.2010907@agliodbs.com> Date: Thu, 29 Jul 2010 10:39:14 -0700 From: Josh Berkus User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9pre) Gecko/20100217 Shredder/3.0.3pre MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: Pooling in Core WAS: Need help in performance tuning. References: <4C37A9C1.1060405@2ndquadrant.com> <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> <20100722212954.GA16758@anarazel.de> <13654.1280263202@sss.pgh.pa.us> <20776.1280282217@sss.pgh.pa.us> <4C5088B1.70902@agliodbs.com> <22316.1280347808@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed 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/448 X-Sequence-Number: 39837 > introduce bugs. If we can get to the point where we have something to > play around with, even if it's kind of kludgey or doesn't quite work, > it'll give us some idea of whether further effort is worthwhile and > how it should be directed. Should I put this on the TODO list, then, in hopes that someone steps forward? -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com