Re: Transaction timeout
От | Japin Li |
---|---|
Тема | Re: Transaction timeout |
Дата | |
Msg-id | ME3P282MB3166AB8DF0381F27C077AF70B69BA@ME3P282MB3166.AUSP282.PROD.OUTLOOK.COM обсуждение исходный текст |
Ответ на | Re: Transaction timeout (Junwang Zhao <zhjwpku@gmail.com>) |
Ответы |
Re: Transaction timeout
|
Список | pgsql-hackers |
On Fri, 22 Dec 2023 at 23:30, Junwang Zhao <zhjwpku@gmail.com> wrote: > On Fri, Dec 22, 2023 at 10:44 PM Japin Li <japinli@hotmail.com> wrote: >> >> >> On Fri, 22 Dec 2023 at 22:37, Junwang Zhao <zhjwpku@gmail.com> wrote: >> > On Fri, Dec 22, 2023 at 10:25 PM Japin Li <japinli@hotmail.com> wrote: >> >> I try to set idle_in_transaction_session_timeout after begin transaction, >> >> it changes immediately, so I think transaction_timeout should also be take >> >> immediately. >> > >> > Ah, right, idle_in_transaction_session_timeout is set after the set >> > command finishes and before the backend send *ready for query* >> > to the client, so the value of the GUC is already set before >> > next command. >> > >> >> I mean, is it possible to set transaction_timeout before next comand? >> > Yeah, it's possible, set transaction_timeout in the when it first > goes into *idle in transaction* mode, see the attached files. > Thanks for updating the patch, LGTM. -- Regrads, Japin Li ChengDu WenWu Information Technology Co., Ltd.
В списке pgsql-hackers по дате отправления: