From:             [EMAIL PROTECTED]
Operating system: linux 2.2
PHP version:      4.0.4pl1
PHP Bug Type:     PostgreSQL related
Bug description:  persistent connections overload

Using Apache 1.3.19, PHP 4.0.4pl1, PgSQL 7.0.3. Web server is RedHat 7.0, PgSQL server 
is RedHat 6.2.

This seems to be the same issue as #8769 and #9185, but I can't edit those, so I'll 
add a new entry since my comments may be helpful.

PHP is apparently not always re-using already opened idle persistent connections. Even 
though there are only a handful of non-idle connections running at any one time, the 
max (currently 256) number of connections eventually gets hit and the database will 
refuse new connections even though it's hardly doing anything.

Right now, my web server has 22 Apache processes running, yet there are 55 Postgres 
processes running, only two of which are not idle.

My installation was already using a static module, so I tried compiling all of Apache 
as one big static, but that had no effect.

Stopping and restarting Apache will clear the idle sessions.

I turned off Apache's keepalive feature, and that seems to have helped somewhat, since 
the Apache child processes now don't stick around so long. However, doing that is a 
performance hit I don't want to take, and it still doesn't explain how I can have more 
Postgres processes than Apache processes.

Any help is greatly appreciated. Long live PHP!

Edit Bug report at:

PHP Development Mailing List <>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to