Subject: Re: Keeping processes open for re-use
From: "Joshua D. Drake" <jd@commandprompt.com>
To: Shane Ambler <pgsql@007Marketing.com>
Cc: Csaba Nagy <nagy@ecircle-ag.com>, Hilary Forbes <hforbes@dmr.co.uk>,
	postgres performance list <pgsql-performance@postgresql.org>
In-Reply-To: <4553DF77.7030000@007Marketing.com>
References: <5.1.0.14.0.20061109123348.0418fbb8@mailserver.dmr.co.uk>
	<1163076964.2839.1.camel@coppola.muc.ecircle.de>
	<4553DF77.7030000@007Marketing.com>
Content-Type: text/plain
Organization: Command Prompt, Inc.
Date: Thu, 09 Nov 2006 18:19:11 -0800
Message-Id: <1163125151.28784.154.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Fri, 2006-11-10 at 12:39 +1030, Shane Ambler wrote:
> Csaba Nagy wrote:
> > On Thu, 2006-11-09 at 13:35, Hilary Forbes wrote:
> >> [snip] Is there a way that we can achieve this in Postgres? We have a
> >> situation whereby we have lots of web based users doing short quick
> >> queries and obviously the start up time for a process must add to
> >> their perceived response time.
> > 
> > Yes: google for "connection pooling". Note that different solutions
> > exist for different programming languages, so you should look for
> > connection pooling for the language you're using.
> > 
> 
> If you are using PHP then persistent connections may be a simpler way if 
> it is enough for your needs.

I would actually suggest pg_pool over pg_pconnect.

Joshua D. Drake


> 
> Basically replace pg_connect with pg_pconnect
> 
> Other languages may have a similar option.
> 
> http://php.net/manual/en/features.persistent-connections.php
> 
> 
-- 

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate