Re: xact_rollback spikes when logical walsender exits

From: Nikolay Samokhvalov <nik(at)postgres(dot)ai>
To: Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Rafael Thofehrn Castro <rafaelthca(at)gmail(dot)com>
Subject: Re: xact_rollback spikes when logical walsender exits
Date: 2026-09-23 16:43:43
Message-ID: CAM527d-pu-rWTjuZ7TEDDO7nGqzBkHi2rM-GdJy46_HrNsP8rw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 8, 2026, Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)com> wrote:
> The patch applies cleanly on master. As experiment I added the tests
> only from 0001 and as expected they failed, but with the patch applied
> they pass. So far so good.

Thanks Mircea. A Windows CI failure while testing this series was in
isolationtester. It exited on connection loss from an intentionally
terminated test session before completing the permutation and teardown.
Andrey's discussion of the test-driver issue is here:

https://www.postgresql.org/message-id/088AB35D-0860-494A-A9CF-8B301543AA51%40yandex-team.ru

This is separate from the xact_rollback accounting change. 0002 still
needs tests.

Nik

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Nikolay Samokhvalov 2026-09-23 16:42:40 Re: injection_points: canceled or terminated waiters leak their wait slots