ID: 13463 Updated by: yohgaki Reported By: [EMAIL PROTECTED] Status: Bogus Bug Type: PostgreSQL related Operating System: FreeBSD 4.4 PHP Version: 4.0.6 New Comment:
I understand your problem, but I think resuing existing connection that has different connection parameter will be a cause of hard to find bug or even a security hole. Older PostgreSQL accepts really few number of connections. 7.1.x supports upto 1024 connections by default (You need to edit postgresql.conf) I suggest to upgrade your server.... -- Yasuo Ohgaki Previous Comments: ------------------------------------------------------------------------ [2001-12-05 21:48:49] [EMAIL PROTECTED] Yes, but my point is that imagine this situation: 40 different usernames for the database 32 maximum connections to the database It doesn't take much to figure out what's going to happen. As soon as the first 32 usernames to be used have created persistent connections, the further 8 usernames can never pconnect -> and remember, that doesn't take into account the fact that there are multiple PHP processes running. So, what I am suggesting is that once all 32 connections are being used and PHP then attempts to use a 33rd username, instead of refusing to open the connection you should destroy the least recently used persistent connection. This could be inefficient, but at least it won't lock PHP out of Postgres. Chris ------------------------------------------------------------------------ [2001-12-05 18:59:06] [EMAIL PROTECTED] This is a design. Connection parameters must be the same to reuse existing persistent connection. This design is useful when you have multiple transactions. ------------------------------------------------------------------------ [2001-09-26 21:44:30] [EMAIL PROTECTED] We never had a problem with persistent connections until we started using about 40 different db usernames/passwords for different scripts on our site, to give the scripts fine grained permissions. Now, the problem is that we rapidly get 40 postmasters appearing, that are not reused. The solution was to switch back to non-persistent connections and everything is hunky dory. I'm fairly certain this problem started appearing in a recent PHP release as one day it wasn't doing it and one day it was, and PHP was upgraded on our servers arount that time. ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=13463&edit=1 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
