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

Поиск
Список
Период
Сортировка
От Barry Lind
Тема Re: Changing behavior of BEGIN...sleep...do something...COMMIT
Дата
Msg-id 3E8E3622.60701@xythos.com
обсуждение исходный текст
Ответ на Re: Changing behavior of BEGIN...sleep...do something...COMMIT  ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>)
Список 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@postgresql.org so that your
> message can get through to the mailing list cleanly
> 



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Kevin Brown
Дата:
Сообщение: Re: Detecting corrupted pages earlier
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Detecting corrupted pages earlier