I think you get a persistent connection per httpd process, no? If this
really is the case, you could then limit your connection count by limiting
the number of times that apache will spawn a new process (10 is default,
IIRC) This isn't exactly true pooling, but should be flexible enough to
meet the intent... :)
Joel
-----Original Message-----
From: Tom Samplonius [mailto:tom@sdf.com]
Sent: Friday, December 22, 2000 11:39 AM
To: Adam Lang
Cc: pgsql-interfaces@postgresql.org
Subject: Re: [INTERFACES] PG on a web-server...issues..and some general
questions on PG deployment
On Fri, 22 Dec 2000, Adam Lang wrote:
> > 3. Is PHP/Postgres module capable of server side connection pooling?
>
> Yes.
The PHP docs are very clear to not referr to it is pooling, but
persistant connections. They are very different things. PHP as a whole
is not capable of pooling, because a separate instance of PHP runs in each
httpd process, and those instances can not shared database connections
between them.
Tom
