Jean-Max Reymond wrote:
2006/11/10, Joshua D. Drake <[EMAIL PROTECTED]>:
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 PH
2006/11/10, Joshua D. Drake <[EMAIL PROTECTED]>:
I would actually suggest pg_pool over pg_pconnect.
Please, can you explain advantages of pg_pool over pg_connect ?
--
Jean-Max Reymond
CKR Solutions Open Source
Nice France
http://www.ckr-solutions.com
---(end of broad
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 obvio
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
Yes. This is connection pooling. You can find a lot of examples from
the internet on connection pooling, rather source codes. Also keep in
mind that connection pools can be maintained on the application as
well as the database server side. Check which one suits you.
--Imad
www.EnterpriseDB.com
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:
Dear All
Looking at the processes running on our server, it appears that each time
a web server program makes a call to the database server, we start a new
process on the database server which obviously has a start up cost. In
Apache, for example, you can say at start up time,that you want the
mac
