Re: [phplib] Problem with permanent connections? From: toby cabot (toby.cabot <email protected>)
Date: 07/07/00

> I feel that, in fact, these new releases work quite well... the
> problem is that after working just a few hours on same PHPlib-
> enabled pages, I've reached the max-client limit of postgres. All on
> my own!!!
> I'm afraid of what could happen when the site will be publicly
> accessible... in a few hours of work I've caused 31 backend
> processes to start.
> Could there be some problems in the way PHPlib (or PHP?)
> handles permanent connection pool? It seems that connections are
> instantiated and never reused.
> Anybody can shed some light?

We'll see. It looks like php sets a limit on persistent database
connections per process, so it would be pretty easy to use a lot of them if
you've got a lot of apache processes running. The php config variable is
pgsql.max_persistent (see also pgsql.max_links). I'd guess that
pgsql.max_persistent times apache MaxClients needs to be less than the max
number of pgsql back ends.

You can run more pg backend processes if you start up the postmaster with
the -N switch. If you try to run too many you may have to tweak your OS
configuration as well.

Toby

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>