Received: from crusher.wdsec.com ([206.215.34.17]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAMEB5s74781 for ; Wed, 22 Nov 2000 09:11:05 -0500 (EST) (envelope-from serge@ephilosopher.com) Received: from landru.wdnis ([192.157.171.30]) by crusher.wdsec.com (8.9.3/8.9.3) with ESMTP id JAA23165; Wed, 22 Nov 2000 09:08:54 -0500 (EST) Received: from ephilosopher.com (crusher [206.215.34.17]) by landru.wdnis (8.8.8+Sun/8.8.8) with ESMTP id JAA00931; Wed, 22 Nov 2000 09:08:53 -0500 (EST) Message-ID: <3A1BD36F.68722F03@ephilosopher.com> Date: Wed, 22 Nov 2000 09:08:47 -0500 From: Serge Canizares X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Itai Zukerman , SQL Subject: Re: Persistent Connects (pg_pconnect) References: <4.3.2.7.2.20001121122024.00b41aa8@192.168.1.253> <87d7foocu7.fsf@matt.w80.math-hat.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200011/183 X-Sequence-Number: 214 > Not sure if this is related, but under the non-threading Apache > server, you get 1 persistent connection per Apache process. I don't > think you can be sure which process gets the page with the connection > request, so if you have a limit of, say, 50 processes, and your server > is hit fairly often, eventually you'll see 50 connections even though > only a few simultaneous accesses to PHP/PostgreSQL are made. > > Or, I could be totally off. > > -itai Actually, with php 4.0x, the apache processes can gather a pool of persistent connexions. I had the same sort of problem once, and saw that each apache process was grabbing ~4 postgreSQL connexions and thus maxing out the number available from the server.