Re: Transaction timeout
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Andrey Borodin <amborodin86@gmail.com>, Michael Paquier <michael.paquier@gmail.com>
Cc: Nikolay Samokhvalov <samokhvalov@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-12-07T18:23:37Z
Lists: pgsql-hackers
Hi, On 2022-12-03 09:41:04 -0800, Andrey Borodin wrote: > Fixed. Added test for this. The tests don't pass: https://cirrus-ci.com/build/4811553145356288 [00:54:35.337](1.251s) not ok 1 - no parameters missing from postgresql.conf.sample [00:54:35.338](0.000s) # Failed test 'no parameters missing from postgresql.conf.sample' # at /tmp/cirrus-ci-build/src/test/modules/test_misc/t/003_check_guc.pl line 81. [00:54:35.338](0.000s) # got: '1' # expected: '0' I am just looking through a bunch of failing CF entries, so I'm perhaps over-sensitized right now. But I'm a bit confused why there's so many occasions of the tests clearly not having been run... Michael, any reason 003_check_guc doesn't show the missing GUCs? It's not particularly helpful to see "0 is different from 1". Seems that even just something like is_deeply(\@missing_from_file, [], "no parameters missing from postgresql.conf.sample"); would be a decent improvement? Greetings, Andres Freund
Commits
-
Add TAP tests for timeouts
- eeefd4280f6e 17.0 landed
-
Remove flaky isolation tests for timeouts
- a661bf7b0f56 17.0 landed
-
Followup fixes for transaction_timeout
- bf82f43790a6 17.0 landed
-
Introduce transaction_timeout
- 51efe38cb92f 17.0 landed
-
On systems that have setsid(2) (which should be just about everything except
- 3ad0728c817b 8.2.0 cited