Bug #8769 Updated: Persistent connections aren't closed when using dynamically loaded module

ID: 8769 Comment by: tinus@deephosting.com Old Reported By: pete@byways.org Reported By: tinus@deephosting.com Status: Closed Bug Type: PostgreSQL related Operating System: RedHat 7.0/Linux 2.2.16 x86 PHP Version: 4.0.4pl1 New Comment: not here. php 4.1.1 and apache 1.3.22. (PostgreSQL 7.1.3). care to tell where you got this information? (about it being fixed Previous Comments: ------------------------------------------------------------------------ [2001-12-11 12:19:48] pete@byways.org Seems to be fixed as of PHP 4.1.0 and Apache 1.3.22 ------------------------------------------------------------------------ [2001-12-05 18:45:27] yohgaki@php.net Status => feedback ------------------------------------------------------------------------ [2001-12-05 18:36:27] yohgaki@php.net Does this happen with 4.1.0RC5? http://www.php.net/~zeev/php-4.1.0RC5.tar.gz ------------------------------------------------------------------------ [2001-01-17 23:01:09] pete@byways.org It seems that either the PostgreSQL connections are not killed after the Apache child process exits, or Apache isn't killing children as normal. If I use the dynamically loaded pgsql module, I run into the maximum number of PostgreSQL clients allowed almost immediately, whereas I have never maxed out the number of clients with the pgsql module compiled into the php library directly. Hope that clears it up. ------------------------------------------------------------------------ [2001-01-17 21:46:44] rasmus@php.net What do you mean by persistent connections not closing? They are not supposed to close, hence the name. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=8769 Edit this bug report at http://bugs.php.net/?id=8769&edit=1