Bug #12558: pgsql connections apparently not being closed
| From: | zeekamotay at hotmail dot com | Date: | Fri, 03 Aug 2001 17:47:02 +0000 |
| Subject: | Bug #12558: pgsql connections apparently not being closed | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-61989@lists.php.net to get a copy of this message | ||
From: zeekamotay@hotmail.com
Operating system: linux
PHP version: 4.0.5
PHP Bug Type: PostgreSQL related
Bug description: pgsql connections apparently not being closed
web server: RedHat 7.0, kernel 2.2, Apache 1.3.20, PHP 4.0.5
db server: RedHat 6.2, kernel 2.2, Postgres 7.1.2
configure:
./configure \
--with-apxs=/usr/local/apache/bin/apxs \
--with-config-file-path=/usr/local/apache/conf \
--disable-xml \
--disable-pear \
--enable-magic-quotes \
--with-curl \
--with-imap \
--without-mysql \
--with-pgsql=/usr/local/pgsql \
--enable-trans-sid \
--with-regex=php \
--enable-memory-limit \
problem:
PHP is apparently not always closing connections to the database server.
At any time, the number of Postgres processes running on the database
server will be 20-100% more than the number of httpd processes running on
the web server.
Eventually, the database server will hit its maximum number of concurrent
connections allowed, and deny further access, even though 90+% of the
running Postgres processes are idle.
This problem exists whether or not I use persistent connections. Turning
off Apache keepalives seems to make the problem much less dramatic (i.e.,
it takes a lot longer to eventually hit the max connections), but it
doesn't cure it.
This problem occurs with PHP 4.0.4pl1 and 4.0.6, and Postgres 7.0.3, as
well. Don't know where to turn next... any ideas? Thanks.
--
Edit bug report at: http://bugs.php.net/?id=12558&edit=1