From: Adam Lang <aalang@rutgersinsurance.com>
To: PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: RE: [HACKERS] PHP and PostgreSQL
Date: Wed, 27 Dec 2000 09:14:40 -0500
Message-ID: <003901c0700f$5a0b8a60$330a0a0a@6014cwpza006> (raw)
References: <183FA749499ED311B6550000F87E206C0C94D1@srv.ctlno.com>
Yeah, this is not a "bug", but a feature. :)
In a nutshell, the persistent connection number is not how many persistent
connections there are available to the webserver. It is the number
available per webserver PROCESS.
So, if you have 5 persistent connections, but 10 webserver processes open,
you have 50 persistent connections open.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Matthew" <matt@ctlno.com>
To: "'Bruce Momjian'" <pgman@candle.pha.pa.us>; "PostgreSQL-development"
<pgsql-hackers@postgresql.org>; "PostgreSQL-interfaces"
<pgsql-interfaces@postgresql.org>
Sent: Wednesday, December 27, 2000 8:54 AM
Subject: [INTERFACES] RE: [HACKERS] PHP and PostgreSQL
>
> I have been asked by the major PHP developer Rasmus Lerdorf to see
> if
> the PostgreSQL/PHP interface needs any improvements.
>
> Is the current PostgreSQL interface module in PHP adequate? Does it
> support all the current libpq features?
>
>
> The only problem we have run into (and I have heard of others having this
> problem also) is with persistent connections. I have seen discussion on
> persistent connection problems but I'm not sure the problem was ever
> resolved. The problem we have seen is that when using persistent
> connections the web server doesn't seen to reuse the connections or
somthing
> to that effect. The result being that we eventually use up our postgres
> limit of 48 connections and nothing can connect to postgre anymore. It is
> possible that this is a configuration problem that we haven't sufficiently
> investigated, but I meniton it because I have heard other talk of this.
> Anyone have more information?
>
> Matthew
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 using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: aalang@rutgersinsurance.com
Subject: Re: RE: [HACKERS] PHP and PostgreSQL
In-Reply-To: <003901c0700f$5a0b8a60$330a0a0a@6014cwpza006>
* 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