From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200102081418.JAA16051@candle.pha.pa.us>
Subject: Re: Re: PostgreSQL and PHP persistent connections
In-Reply-To: <200102081310.IAA03647@jupiter.greatbridge.com> "from Jan Wieck
	at Feb 8, 2001 08:10:11 am"
To: Jan Wieck <janwieck@Yahoo.com>
Date: Thu, 8 Feb 2001 09:18:25 -0500 (EST)
CC: Tom Lane <tgl@sss.pgh.pa.us>, "Thies C. Arntzen" <thies@digicol.de>,
	rasmus@php.net, PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

> > > How is that an improvement?  It only changes the case in which you get
> > > a NOTICE from not-in-transaction to in-transaction ...
> >
> > Well, the most common case is that you are not in a transaction.
> 
>     Why   not   tracing  PQcmdStatus(result)  on  the  persistent
>     connection?  It  allways   returns   "BEGIN",   "COMMIT"   or
>     "ROLLBACK" for whatever you issued.
> 
>     Well,  it'll  not  catch the uncommon case that someone might
>     issue  multiple  queries   in   one   statements   (semicolon
>     separated). But that's IMHO bad practice anyway and the above
>     will avoid communication, context switching and eating up  of
>     XID's until we have silent rollback in 7.2.

It is the multi-command issue that prevented me from suggesting checking
the return status.  If they are leaving an open transaction after
disconnecting, they could be doing any crazy thing.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026