pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thies C. Arntzen <thies@thieso.net>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Thies C. Arntzen <thies@digicol.de>
Cc: rasmus@php.net, PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: PostgreSQL and PHP persistent connections
Date: Fri, 9 Feb 2001 16:39:35 +0100
Message-ID: <20010209163935.A23742@schnuffel.thieso.net> (raw)
In-Reply-To: <200102091519.KAA02853@candle.pha.pa.us>
References: <20010209144154.A23220@schnuffel.thieso.net>
	<200102091519.KAA02853@candle.pha.pa.us>

On Fri, Feb 09, 2001 at 10:19:51AM -0500, Bruce Momjian wrote:
> > > We discussed using 'ROLLBACK' before passing a connection to a new user,
> > > but the problem was that ROLLBACK with no open transaction causes a
> > > server log error message.  We discussed adding 'ROLLBACK SILENT' to fix
> > > this, but I believe a better, more portable solution is a simple "BEGIN
> > > WORK;ROLLBACK".  This will do nothing if there is no open transaction,
> > > and will ROLLBACK any open transaction.  I propose this be sent by PHP
> > > as the first query when passing persistent connections.
> > 
> >     was there a conclusion made yet (that i missed somehow) on
> >     this subject? i'd like to implement *something* in the PHP
> >     core for this soon.
> 
> One person objected that BEGIN;ROLLBACK will throw an error to the log
> file if there was an open transaction, but I think that is fine as this
> is a rare occurance, and an argument can be made that leaving an open
> transaction on session close in a pooled connection environment should
> throw some kind of error anyway.  Also, this fix will work for all
> versions of PostgreSQL, so it can be implemented right away with no
> backend changes or version checks.

    ok, i'll start playing around with this solution soon. i'll
    commit it to the PHP 4 cvs as soon as i'm happy with it.

    thies
> 
> We still need a global RESET, but I don't think that can be done until
> 7.2.  I will add that to our project TODO list.



view thread (17+ messages)  latest in thread

Message-ID: <20010209163935.A23742@schnuffel.thieso.net>
Permalink:  ../20010209163935.A23742@schnuffel.thieso.net/
Also on:    postgresql.org/message-id/20010209163935.A23742@schnuffel.thieso.net

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: thies@thieso.net, pgman@candle.pha.pa.us, thies@digicol.de
  Subject: Re: PostgreSQL and PHP persistent connections
  In-Reply-To: <20010209163935.A23742@schnuffel.thieso.net>

* 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