From: Adam Lang <aalang@rutgersinsurance.com>
To: pgsql-php@postgresql.org
Subject: Re: persistent vs. non-persistent
Date: Thu, 4 Oct 2001 09:01:40 -0400
Message-ID: <009401c14cd4$b5eefa40$330a0a0a@rutgersinsurance.com> (raw)
References: <20011001213819.82F8B2AB46@bugs.unl.edu.ar>
<01a301c14ac2$908990d0$1e51000a@mitch>
<20011001225313.C81032AB46@bugs.unl.edu.ar>
<01d501c14acc$54b3d520$1e51000a@mitch>
<20011002112117.A31207@rakete.joerdens.de>
You are correct. It is not max per Apache, but max per child process.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Frank Joerdens" <frank@joerdens.de>
To: <pgsql-php@postgresql.org>
Sent: Tuesday, October 02, 2001 5:21 AM
Subject: Re: [PHP] persistent vs. non-persistent
> On Mon, Oct 01, 2001 at 06:56:37PM -0400, Mitch Vincent wrote:
> > I'm not sure about the internal workings, I see what you mean and will
await
> > your finding with great interest!
> >
> > -Mitch
>
> [ . . . ]
> > > I don't understand why apache (or PHP) doesn't see that it has a
> > persistent
> > > database connection open to use.
> > >
> > > I'm checking the PHP PGSQL extensions at this moment.
> > > More info later....
> > >
> > > Saludos.... ;-)
>
> I keep having problems too; I think because I never quite managed to
> figure out the mechanism either. Sometime last year someone mentioned
> that the php.ini parameters
>
> pgsql.max_links
> pgsql.max_persistent
>
> are meant to be understood as /per Apache child/; so if you have, say, 5
> Apache children waiting for a request, and
>
> pgsql.max_persistent = 2
>
> you could have up to 10 open connections. If an apache child which does
> not have an open connection gets a request, it will open a new
> connection, obviously. So if 4 of the 5 Apache children have open
> connections, but the 5th gets the next request, a new connection will be
> opened. I am not sure about what happens when a child which already has
> an open connection gets a new request. Hypothesis: It depends on the
> database. Say you have 3 distinct databases on your server and your
> php.ini parameter
>
> pgsql.max_persistent = 2
>
> Now let's say you have 10 open Apache children, each of which has a
> connection to databases #1 and #2. Now requests to databases #1 and #2
> will be answered, but not to #3: You'll get the error message:
>
> Warning: PostgreSQL: Too many open persistent links (2)
>
> My tests seem to confirm this.
>
> It would seem to follow that you only need as many persistent
> connections per Apache child as you have databases from which you want
> to serve http requests.
>
> Regards, Frank
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: aalang@rutgersinsurance.com
Subject: Re: persistent vs. non-persistent
In-Reply-To: <009401c14cd4$b5eefa40$330a0a0a@rutgersinsurance.com>
References: <20011001213819.82F8B2AB46@bugs.unl.edu.ar> <01a301c14ac2$908990d0$1e51000a@mitch> <20011001225313.C81032AB46@bugs.unl.edu.ar> <01d501c14acc$54b3d520$1e51000a@mitch> <20011002112117.A31207@rakete.joerdens.de> <009401c14cd4$b5eefa40$330a0a0a@rutgersinsurance.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox