Re: Feature freeze date for 8.1

Поиск
Список
Период
Сортировка
Искать
От
Neil Conway
Тема
Re: Feature freeze date for 8.1
Дата
в 01:14:54
Msg-id
4275A933.1050608@samurai.com
Ответ на
Список
Дерево обсуждения
Re: Feature freeze date for 8.1 <adnandursun@asrinbilisim.com.tr>
Re: Feature freeze date for 8.1 Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: Feature freeze date for 8.1 Dennis Bjorklund <db@zigo.dhs.org>
Re: Feature freeze date for 8.1 <adnandursun@asrinbilisim.com.tr>
Oliver Jowett wrote:
> I raised this a while back on -hackers:
> 
>   http://archives.postgresql.org/pgsql-hackers/2005-02/msg00397.php
> 
> but did not get much feedback.

Perhaps you can interpret silence as consent? :)

> Does anyone have comments on that email?

I wouldn't be opposed to it. It would be different than 
statement_timeout, in that we'd be measuring transaction *idle* time, 
not total transaction runtime, so perhaps "transaction_idle_timeout" is 
a better name than "transaction_timeout". Also, presumably when the 
transaction idle timeout fires, we should just rollback the current 
transaction, not close the client connection -- so you could potentially 
have idle backends sticking around for the full TCP timeout period. 
Since they shouldn't be holding any locks I don't see that as a big problem.

-Neil

В списке pgsql-hackers по дате отправления
От: Jaime Casanova
Дата:
От: Tom Lane
Дата:
FAQ