X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id BA1569FA5BA for ; Sat, 3 Jun 2006 12:36:04 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 76566-02 for ; Sat, 3 Jun 2006 12:35:56 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by postgresql.org (Postfix) with ESMTP id B584F9FA311 for ; Sat, 3 Jun 2006 12:35:55 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id a2so824422ugf for ; Sat, 03 Jun 2006 08:35:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hqk8a3LNjcEPz671Igvu81EseCKRytyhGMZz4ufsDYLbJ4WoJgC0b2zNAG/anpszxqJq/lXwcPPYnhaDLY7Epy4XWcQEgQEdQp7mHYonUEymveW0gJADpCEnfR9oNhzJ/Bl0F1aS2EpKKF2CA43qz9Dmf+J36m5y8/6zZHnRkpY= Received: by 10.67.30.6 with SMTP id h6mr1766864ugj; Sat, 03 Jun 2006 08:35:54 -0700 (PDT) Received: by 10.67.92.4 with HTTP; Sat, 3 Jun 2006 08:35:54 -0700 (PDT) Message-ID: Date: Sat, 3 Jun 2006 16:35:54 +0100 From: "Neil Saunders" To: pgsql-performance@postgresql.org Subject: Re: scaling up postgres In-Reply-To: <4481A856.7050907@boreham.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200606030931.k539V38Y007877@smtp2.planet.net.tn> <15971.1149347558@sss.pgh.pa.us> <4481A856.7050907@boreham.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/25 X-Sequence-Number: 19382 > > Tom Lane wrote: > As per PFC's comment, if connections/sec is a bottleneck for you then the > answer is to use persistent connections. Launching a new backend is a fairly > heavyweight operation in Postgres. > In which case maybe pgpool could help in this respect? http://pgpool.projects.postgresql.org/ Cheers, Neil.