Re: Keeping processes open for re-use - Mailing list pgsql-performance

From Richard Huxton
Subject Re: Keeping processes open for re-use
Date
Msg-id 455D9B14.7030407@archonet.com
Whole thread Raw
In response to Re: Keeping processes open for re-use  ("Jean-Max Reymond" <jmreymond@gmail.com>)
List pgsql-performance
Jean-Max Reymond wrote:
> 2006/11/10, Joshua D. Drake <jd@commandprompt.com>:
>>
>> I would actually suggest pg_pool over pg_pconnect.
>>
>
> Please, can you explain advantages of pg_pool over pg_connect ?

He said pg_pconnect (note the extra "p"). This provides permanent
connections to the database from PHP. However, you will end up with one
connection per Apache process running (without running multiple Apache
setups to serve different content types). Since many processes will be
serving images or static content you have a lot of wasted, idle,
connections.

Now, pg_pool allows you to maintain a small number of active connections
(say 20 or 50) and have PHP connect to your pgpool server. It allocates
the next free connection it holds and so lets you minimise the number of
connections to PostgreSQL.

HTH
--
   Richard Huxton
   Archonet Ltd

pgsql-performance by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: [BUGS] BUG #2737: hash indexing large tablefails,while btree of same index works
Next
From: "Simon Riggs"
Date:
Subject: Re: [BUGS] BUG #2737: hash indexing largetablefails,while btree of same index works