Received: from mail3.mx.voyager.net (mail3.mx.voyager.net [216.93.66.202]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f91Llcn39497 for ; Mon, 1 Oct 2001 17:47:39 -0400 (EDT) (envelope-from mvincent@cablespeed.com) Received: from mitch (216-93-124-123.mdmmi.voyager.net [216.93.124.123]) by mail3.mx.voyager.net (8.11.6/8.10.2) with SMTP id f91LlaA52902 for ; Mon, 1 Oct 2001 17:47:36 -0400 (EDT) Message-ID: <01a301c14ac2$908990d0$1e51000a@mitch> From: "Mitch Vincent" To: References: <20011001213819.82F8B2AB46@bugs.unl.edu.ar> Subject: Re: persistent vs. non-persistent Date: Mon, 1 Oct 2001 17:46:44 -0400 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.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Archive-Number: 200110/9 X-Sequence-Number: 562 > I'm having headaches with PHP, postgres and persistent connections. They never have really worked for me, but I haven't tried with the recent PHP->PGSQL improvements.. > The problem is that my postgres backends stay alive after closing the > connection. That's what a persistant connection is, though... You'll have as many minimum PG backends hanging around as you do minimum apache backends (once that many PG backends get started, they hang around). > I use pg_pconnect to connect to the database, put after closing the > conection, nothing happens, la backend stays alive, and all I can do is > restart apache to make them close (really close). > > Any solution to this? Sure, don't use persistant connections..It sounds like they're the opposite of what you want... -Mitch