Received: from snoopy.mohawksoft.com (216.41.12.host227 [216.41.12.227] (may be forged)) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f02DTML77218; Tue, 2 Jan 2001 08:29:22 -0500 (EST) (envelope-from markw@mohawksoft.com) Received: from mohawksoft.com (IDENT:markw@snoopy.mohawksoft.com [216.41.12.227]) by snoopy.mohawksoft.com (8.11.0/8.11.0) with ESMTP id f02DVk618697; Tue, 2 Jan 2001 08:31:46 -0500 Message-ID: <3A51D842.5946D89@mohawksoft.com> Date: Tue, 02 Jan 2001 08:31:46 -0500 From: mlw X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16-Mohawk i686) X-Accept-Language: en MIME-Version: 1.0 CC: PostgreSQL-development , PostgreSQL-interfaces Subject: Re: [INTERFACES] Re: PHP and PostgreSQL References: <200101020716.CAA09459@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200101/31 X-Sequence-Number: 2703 Bruce Momjian wrote: > > Does this requested chagne have to do with Apache or PostgreSQL? > I suspect it is a request that live postgresql processes can linger around after a connection is completed and be re-assigned to a new connection as soon as one comes along. This will save the startup cost of a new postgresql process. This is what apache does. -- http://www.mohawksoft.com