Re: Transaction timeout

x4mmm@yandex-team.ru

From: "Andrey M. Borodin" <x4mmm@yandex-team.ru>

To: Alexander Korotkov <aekorotkov@gmail.com>

Cc: Japin Li <japinli@hotmail.com>, Peter Smith <smithpb2250@gmail.com>, Junwang Zhao <zhjwpku@gmail.com>, 邱宇航 <iamqyh@gmail.com>, Fujii Masao <masao.fujii@oss.nttdata.com>, Andrew Borodin <amborodin86@gmail.com>, Michael Paquier <michael.paquier@gmail.com>, Nikolay Samokhvalov <samokhvalov@gmail.com>, pgsql-hackers mailing list <pgsql-hackers@postgresql.org>, pgsql-hackers mailing list <pgsql-hackers@lists.postgresql.org>, Andres Freund <andres@anarazel.de>

Date: 2024-03-12T08:28:19Z

Lists: pgsql-hackers

Attachments

v4-0001-Add-timeouts-TAP-tests.patch (application/octet-stream) patch v4-0001


> On 11 Mar 2024, at 16:18, Alexander Korotkov <aekorotkov@gmail.com> wrote:
> 
> I think if checking psql stderr is problematic, checking just logs is
> fine.  Could we wait for the relevant log messages one by one with
> $node->wait_for_log() just like 040_standby_failover_slots_sync.pl do?

PFA version with $node->wait_for_log()

Best regards, Andrey Borodin.

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