Received: from bush.rutgersinsurance.com (rutgersinsurance.com [38.138.71.194]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBREAjL17984 for ; Wed, 27 Dec 2000 09:10:45 -0500 (EST) (envelope-from aalang@rutgersinsurance.com) Received: from 6014cwpza006 ([10.10.10.51]) by bush.rutgersinsurance.com (8.9.3/8.9.3) with SMTP id JAA17501 for ; Wed, 27 Dec 2000 09:15:16 -0500 Message-ID: <003901c0700f$5a0b8a60$330a0a0a@6014cwpza006> From: "Adam Lang" To: "PostgreSQL-interfaces" References: <183FA749499ED311B6550000F87E206C0C94D1@srv.ctlno.com> Subject: Re: RE: [HACKERS] PHP and PostgreSQL Date: Wed, 27 Dec 2000 09:14:40 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200012/222 X-Sequence-Number: 568 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" To: "'Bruce Momjian'" ; "PostgreSQL-development" ; "PostgreSQL-interfaces" 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