Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E619F632810 for ; Fri, 9 Jul 2010 19:59:24 -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 70264-02 for ; Fri, 9 Jul 2010 22:59:17 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mail.postgresql.org (Postfix) with ESMTP id 4E3146327D0 for ; Fri, 9 Jul 2010 19:59:17 -0300 (ADT) Received: from [192.168.1.208] (81-179-24-86.dsl.pipex.com [81.179.24.86]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0M8b3L-1PIsoz1qnj-00vyLO; Sat, 10 Jul 2010 00:59:15 +0200 Message-ID: <4C37A9C1.1060405@2ndquadrant.com> Date: Fri, 09 Jul 2010 23:59:13 +0100 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Matthew Wakeling CC: Kevin Grittner , Brad Nicholson , pgsql-performance@postgresql.org, Tom Lane Subject: Re: Need help in performance tuning. References: <4C369346.6010501@postnewspapers.com.au> <8760.1278650566@sss.pgh.pa.us> <1278680186.1914.36.camel@bnicholson-desktop> <4C36F57102000025000332F6@gw.wicourts.gov> <4C36FEAD02000025000332FC@gw.wicourts.gov> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:QNrgt61JaUBdcD2heOQljRKiRENLUSQIUL5emY2IlZ6 fsIU6hKU8LgiGEF/l6rAc0jyeGj3KtpotOpcdl3RcZHLr4fcku b2MB2PBKQpB61LuK7hEgmKB5rTApDX9npUuWtO2XJy6O7+CSjK btD9ncrLNLg47+tJEEd4cVshz9Hxvb89OHwHX5SGNMvRuUR6ZA Hq+Qj3pGSHzB+mvtMZ189081XoSXNRFJiiIuceMdj8= 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, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201007/163 X-Sequence-Number: 39552 Matthew Wakeling wrote: > If you have an external pool solution, you can put it somewhere else - > maybe on multiple somewhere elses. This is the key point to observe: if you're at the point where you have so many connections that you need a pool, the last place you want to put that is on the overloaded database server itself. Therefore, it must be an external piece of software to be effective, rather than being part of the server itself. Database servers are relatively expensive computing hardware due to size/quantity/quality of disks required. You can throw a pooler (or poolers) on any cheap 1U server. This is why a built-in pooler, while interesting, is not particularly functional for how people normally scale up real-world deployments. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us