pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mitch Vincent <mvincent@cablespeed.com>
To: Martín Marqués <martin@bugs.unl.edu.ar>
To: pgsql-php@postgresql.org
Subject: Re: persistent vs. non-persistent
Date: Mon, 1 Oct 2001 18:56:37 -0400
Message-ID: <01d501c14acc$54b3d520$1e51000a@mitch> (raw)
References: <20011001213819.82F8B2AB46@bugs.unl.edu.ar>
	<01a301c14ac2$908990d0$1e51000a@mitch>
	<20011001225313.C81032AB46@bugs.unl.edu.ar>

I'm not sure about the internal workings, I see what you mean and will await
your finding with great interest!

-Mitch

----- Original Message -----
From: "Martín Marqués" <martin@bugs.unl.edu.ar>
To: <pgsql-php@postgresql.org>
Sent: Monday, October 01, 2001 6:53 PM
Subject: Re: [PHP] persistent vs. non-persistent


> On Lun 01 Oct 2001 18:46, you wrote:
> > > 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...
>
> I've been all day looking for solid info on this case, and what I thought
is
> this:
>
> Is there a way to seek for open db connections?
>
> I don't understand why apache (or PHP) doesn't see that it has a
persistent
> database connection open to use.
>
> I'm checking the PHP PGSQL extensions at this moment.
> More info later....
>
> Saludos.... ;-)
>
> --
> Porqué usar una base de datos relacional cualquiera,
> si podés usar PostgreSQL?
> -----------------------------------------------------------------
> Martín Marqués                  |        mmarques@unl.edu.ar
> Programador, Administrador, DBA |       Centro de Telematica
>                        Universidad Nacional
>                             del Litoral
> -----------------------------------------------------------------
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>




view thread (14+ messages)  latest in thread

Message-ID: <01d501c14acc$54b3d520$1e51000a@mitch>
Permalink:  ../01d501c14acc$54b3d520$1e51000a@mitch/
Also on:    postgresql.org/message-id/01d501c14acc$54b3d520$1e51000a@mitch

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: mvincent@cablespeed.com, martin@bugs.unl.edu.ar
  Subject: Re: persistent vs. non-persistent
  In-Reply-To: <01d501c14acc$54b3d520$1e51000a@mitch>
  References: <20011001213819.82F8B2AB46@bugs.unl.edu.ar> <01a301c14ac2$908990d0$1e51000a@mitch> <20011001225313.C81032AB46@bugs.unl.edu.ar> <01d501c14acc$54b3d520$1e51000a@mitch>

* 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