Basically, after so many people connect and disconnect, the PHP doesn't
reuse/drop old connections so you maximum amount is reached. You'd get to
the point where no one is connected, but one another person would try to and
it would come back with an error saying no connections available.
I am unaware if anything has been posted to PHP about it.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Frank Joerdens" <frank@joerdens.de>
To: "The Hermit Hacker" <scrappy@hub.org>
Cc: "Charles Tassell" <ctassell@isn.net>; "Adam Lang"
<aalang@rutgersinsurance.com>; <pgsql-general@postgresql.org>;
<scherf@ventasoft.de>
Sent: Thursday, November 16, 2000 1:08 PM
Subject: Re: [HACKERS] Re: [GENERAL] PHPBuilder article -- Postgres vs MySQL
> The Hermit Hacker wrote:
> >
> > On Wed, 15 Nov 2000, Charles Tassell wrote:
> >
> > > Just a note, I've been using Postgres 7.02 and PHP 4.02 or 4.03 for
about a
> > > month in a couple sites, and haven't experienced any problems with
> > > persistent connections. Problem might have been fixed in one of the
point
> > > releases, or maybe I just don't have enough different db connections
to
> > > trigger it.
> >
> > I run PHP4 and IMP (http://www.horde.org) and we've gotten then to
remove
> > the useof pg_pconnect() since it is broken. Broken how, you might
> > ask? Well, I ran on a standalone machine, no other web users but
myself,
> > to test, and each tim eI hit the database with IMP,. it opened a new
> > backend, but it never reused old, idle ones ... eventually, you run out
of
> > the ability to connect since you've locked up all connections ...
>
> That sounds pretty evil. Have you also tested PHP3 by any chance? Has this
been posted to
> php-general? If this is a general issue, it would have to be considered a
_very_ nasty bug
> indeed. Can you describe how you made the test, i.e. how you saw that it
wouldn't reuse
> idle ones and keeps opening new ones? How would you monitor this?
>
> - Frank
