From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200303182218.h2IMI2I13909@candle.pha.pa.us>
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
In-Reply-To: <Pine.LNX.4.44.0303181551230.3331-100000@peter.localdomain>
To: Peter Eisentraut <peter_e@gmx.net>
Date: Tue, 18 Mar 2003 17:18:02 -0500 (EST)
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
	PostgreSQL Development <pgsql-hackers@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

Peter Eisentraut wrote:
> Bruce Momjian writes:
> 
> > What if folks want all their connections autocommit off.
> 
> For interactive use, people can record their preferred setting in
> ~/.psqlrc or something like that.

But that only works for psql, right?  How would this be done at the
libpq level?  Environment variables?  GUC seems a whole lot cleaner.

> But any non-interactive program is written with a specific autocommit
> setting in mind.  Either it assumes that single statements are
> automatically committed or it issues explicit COMMIT commands.  That
> means, the choice of autocommit mode is always ultimately determined by
> the client, never by the server or its administrator.
> 
> For that very reason most standard interfaces define in their
> specification whether applications must assume autocommit behavior or must
> not do so.

I understand.  I just don't see any value in pushing that logic into
each client when we can do it centrally in the server.

-- 
  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