From: Shane Ambler <pgsql@007Marketing.com>
To: Csaba Nagy <nagy@ecircle-ag.com>
Cc: Hilary Forbes <hforbes@dmr.co.uk>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: Keeping processes open for re-use
Date: Fri, 10 Nov 2006 12:39:59 +1030
Message-ID: <4553DF77.7030000@007Marketing.com> (raw)
In-Reply-To: <1163076964.2839.1.camel@coppola.muc.ecircle.de>
References: <5.1.0.14.0.20061109123348.0418fbb8@mailserver.dmr.co.uk>
<1163076964.2839.1.camel@coppola.muc.ecircle.de>
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.
Basically replace pg_connect with pg_pconnect
Other languages may have a similar option.
http://php.net/manual/en/features.persistent-connections.php
--
Shane Ambler
pgSQL@007Marketing.com
Get Sheeky @ http://Sheeky.Biz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pgsql@007Marketing.com, nagy@ecircle-ag.com, hforbes@dmr.co.uk
Subject: Re: Keeping processes open for re-use
In-Reply-To: <4553DF77.7030000@007Marketing.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox