| From: | Shane Ambler <pgsql(at)007Marketing(dot)com> |
|---|---|
| To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
| Cc: | Hilary Forbes <hforbes(at)dmr(dot)co(dot)uk>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Keeping processes open for re-use |
| Date: | 2006-11-10 02:09:59 |
| Message-ID: | 4553DF77.7030000@007Marketing.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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(at)007Marketing(dot)com
Get Sheeky @ http://Sheeky.Biz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-11-10 02:19:11 | Re: Keeping processes open for re-use |
| Previous Message | imad | 2006-11-09 17:55:41 | Re: Keeping processes open for re-use |