From: | Frank Bax <fbax(at)sympatico(dot)ca> |
---|---|
To: | pgsql-php(at)postgresql(dot)org |
Subject: | Re: too many clients |
Date: | 2004-12-30 20:34:15 |
Message-ID: | 5.2.1.1.0.20041230153137.00a63740@pop6.sympatico.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-php |
Wrong - if username changes, another connection to same database is used
within the same apache child process. Everything in the connect string
must be the same before a persistent connection is reused.
At 01:45 PM 12/30/04, Gavin M. Roy wrote:
>Yes, php opens 1 persistant connection per apache backend per database.
>
>On Thu, 2004-12-30 at 09:03 -0500, Matthew Terenzio wrote:
> > >
> > >
> > > On Thu, 2004-12-30 at 00:20 -0500, Greg Stark wrote:
> > >> "Gavin M. Roy" <gmr(at)ehpg(dot)net> writes:
> > >>
> > >>> I use it on a few very high traffic sites without issue, but it is
> > >>> tuned so
> > >>> that there is only 1 persistant connection per apache backend and
> > >>> postgresql
> > >>> will allow the max apache backends, which by default is generally
> > >>> 256. I
> > >>> highly recommend it in such a situation, while I generally do not
> > >>> recommend
> > >>> it in any other.
> > So if I have one Postgres installation but two databases, is it
> > possible that PHP would create twice as many persistant connections as
> > apache childs? This may be where my understanding went awry.
> > >
> > > ---------------------------(end of
> > > broadcast)---------------------------
> > > TIP 4: Don't 'kill -9' the postmaster
> >
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
From | Date | Subject | |
---|---|---|---|
Next Message | Michelle Konzack | 2005-01-18 14:39:44 | base64 encoded images plus php |
Previous Message | Gavin M. Roy | 2004-12-30 18:45:36 | Re: too many clients |