Re: [phplib] Problem with permanent connections? From: Bob Bowker (bowker <email protected>)
Date: 07/08/00

Hi --

The subject of "too many connections" has been tossed around here and on
the PHP lists several times in the past year, and I have missed it if
anyone has come up with an explanation ...

The only fact of which I'm sure is that, as soon as I changed PHPLib's
"p_connect" to "connect", the problem disappeared. This experience has
held true on several different hosts around the country for both virtual
and dedicated clients, for SCO and RH and FreeBSD, for heavy-load sites
and ego sites ...

Bob.

toby cabot wrote:
>
> > > I'd guess that
> > > pgsql.max_persistent times apache MaxClients needs to be less than the
> max
> > > number of pgsql back ends.
> > >
> >
> > This surprises me a little. I thought there were a 1:1 relation
> > between apache child processes and database connections. Why
> > a http server process should need more than one database
> > connection?
>
> I think it keeps one connection per database/uid pair. So if you need to
> connect to two different db's, or one db but as two different users then
> you'll keep additional persistent connections. If you have your own
> personal database and then a shared test database you'll have two
> connections open.
>
> I've noticed this because I use a few different php applications, and each
> has its own database. But I use very few apache processes so it's OK.
>
> Toby
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: phplib-unsubscribe <email protected>
> For additional commands, e-mail: phplib-help <email protected>

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>