Re: Changing behavior of BEGIN...sleep...do something...COMMIT

From: Barry Lind <blind(at)xythos(dot)com>
To: Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Olleg Samojlov <olleg(at)jane(dot)telecom(dot)mipt(dot)ru>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Changing behavior of BEGIN...sleep...do something...COMMIT
Date: 2003-04-05 01:49:22
Message-ID: 3E8E3622.60701@xythos.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Brown 2003-04-05 01:52:46 Re: Detecting corrupted pages earlier
Previous Message Tom Lane 2003-04-05 00:22:58 Re: more contrib: log rotator