Horton

Re: Transaction timeout

x4mmm@yandex-team.ru

View thread View on postgr.es
From: "Andrey M. Borodin" <x4mmm@yandex-team.ru>
To: Junwang Zhao <zhjwpku@gmail.com>
Cc: Li Japin <japinli@hotmail.com>, 邱宇航 <iamqyh@gmail.com>, Fujii Masao <masao.fujii@oss.nttdata.com>, Andrey Borodin <amborodin86@gmail.com>, Andres Freund <andres@anarazel.de>, Michael Paquier <michael.paquier@gmail.com>, Nikolay Samokhvalov <samokhvalov@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2024-01-03T11:46:36Z
Lists: pgsql-hackers 

> On 3 Jan 2024, at 11:39, Andrey M. Borodin <x4mmm@yandex-team.ru> wrote:
> 
> 
> 
>> On 1 Jan 2024, at 19:28, Andrey M. Borodin <x4mmm@yandex-team.ru <mailto:x4mmm@yandex-team.ru>> wrote:
>> 
>>  3. Check that timeout is not rescheduled by new queries (Nik's case)
> 
> The test of Nik's case was not stable enough together with COMMIT AND CHAIN. So I've separated these cases into different permutations.
> Looking through CI logs it seems variation in sleeps and actual timeouts easily reach 30+ms. I'm not entirely sure we can reach 100% stable tests without too big timeouts.
> 
> 
> Best regards, Andrey Borodin.
> 
> <v21-0001-Introduce-transaction_timeout.patch>
> <v21-0002-Add-better-tests-for-transaction_timeout.patch>
> <v21-0003-Try-to-enable-transaction_timeout-before-next-co.patch>
> <v21-0004-fix-reschedule-timeout-for-each-commmand.patch>
 I do not understand why, but mailing list did not pick patches that I sent. I'll retry.


Best regards, Andrey Borodin.

Commits

  1. Add TAP tests for timeouts

  2. Remove flaky isolation tests for timeouts

  3. Followup fixes for transaction_timeout

  4. Introduce transaction_timeout

  5. On systems that have setsid(2) (which should be just about everything except