From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200303211746.h2LHk2912957@candle.pha.pa.us>
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
In-Reply-To: <14030.1048268545@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 21 Mar 2003 12:46:02 -0500 (EST)
Cc: Peter Eisentraut <peter_e@gmx.net>,
	Alvaro Herrera <alvherre@dcc.uchile.cl>,
	PostgreSQL Development <pgsql-hackers@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Peter Eisentraut wrote:
> >> The standard only covers embedded C programs.  Other interfaces that are
> >> covered by other standards require other settings.
> 
> > My point was that _the_ standard requires autocommit off, not that
> > everyone is using autocommit off.
> 
> Peter's point is good: the only interface that is actually subject to the
> part of the spec you are quoting is ecpg.  It could reasonably be argued
> that libpq should only support autocommit-on, because that's the
> historical behavior that programs written atop libpq expect.  The other
> client libraries have their own specs to adhere to.

But isn't that like saying that the spec doesn't apply to libpq at all. 
Why would autocommit not apply but other queries specification apply?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073