
> Also, per other discussions, we are removing backend autocommit support
> in 7.4.  It was the wrong way to do it.

Somehow I did not see that conclusion made.
I thought, at least for JDBC, it is already successfully used ?
I think the backend autocommit is useful. Maybe only the 
installation/database/user wide GUC setting should be depricated/
disabled, so it is only used by a session SET ?

Andreas


Fri, 4 Apr 2003 13:43:41 +0200
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: Changing behavior of BEGIN...sleep...do something...COMMIT 
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at> writes:
> Somehow I did not see that conclusion made.
> I thought, at least for JDBC, it is already successfully used ?

Barry, at least, seemed to be happy with removing it, given the planned
protocol change to report current transaction state after every query.

> I think the backend autocommit is useful. Maybe only the 
> installation/database/user wide GUC setting should be depricated/
> disabled, so it is only used by a session SET ?

That wouldn't really solve any of the problems.

			regards, tom lane


Fri, 04 Apr 2003 09:25:13 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: Changing behavior of BEGIN...sleep...do something...COMMIT 
Zeugswetter Andreas SB SD wrote:
> 
> > Also, per other discussions, we are removing backend autocommit support
> > in 7.4.  It was the wrong way to do it.
> 
> Somehow I did not see that conclusion made.
> I thought, at least for JDBC, it is already successfully used ?
> I think the backend autocommit is useful. Maybe only the 
> installation/database/user wide GUC setting should be depricated/
> disabled, so it is only used by a session SET ?

Yes, I agree, but most of the other folks think autocommit shouldn't be
in the backend.

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


Fri, 4 Apr 2003 09:37:45 -0500 (EST)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: Changing behavior of BEGIN...sleep...do something...COMMIT
Andreas,

 From the JDBC side it really doesn't make that much difference.  The 
JDBC code needs to support both ways of doing it (explicit begin/commits 
for 7.2 and earlier servers, and set autocommit for 7.3 servers), so 
however it ends up for 7.4 it shouldn't be too much work to adopt.  As 
Tom has mentioned elsewhere the key change is having the FE/BE protocol 
report the current transaction state.

thanks,
--Barry


Zeugswetter Andreas SB SD wrote:
>>Also, per other discussions, we are removing backend autocommit support
>>in 7.4.  It was the wrong way to do it.
> 
> 
> Somehow I did not see that conclusion made.
> I thought, at least for JDBC, it is already successfully used ?
> I think the backend autocommit is useful. Maybe only the 
> installation/database/user wide GUC setting should be depricated/
> disabled, so it is only used by a session SET ?
> 
> Andreas
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
> 


Fri, 04 Apr 2003 17:49:22 -0800
Barry Lind <blind@xythos.com>
Re: Changing behavior of BEGIN...sleep...do something...COMMIT