Re: [PATCH] Fix ProcKill lock-group vs procLatch recycle race

Vlad Lesin <vladlesin@gmail.com>

From: Vlad Lesin <vladlesin@gmail.com>

To: Andrey Borodin <x4mmm@yandex-team.ru>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-05-05T16:31:36Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix procLatch ownership race in ProcKill()
- 84b9d6bceab6 19 (unreleased) cited

Andrey, thank you for your fixes.

On 5/5/26 12:07, Andrey Borodin wrote:

> To help resolve this confusion I'm posting following sequence:
> 
> 1. vAB1-0001-Add-regression-test-for-ProcKill-lock-group-pro.patch
> This is an original test that is expected to demonstrate problem.
> It contains heavy injection points refactoring, I assume it's not intended for commit.
> This test was taken from a file 0003-PG18-unfixed-repro-tap-injection-harness.patch
> 
> 2. vAB1-0002-Canonicalize-test-with-infrastructure.patch
> My changes needed to make test runnable.
> 
> 3. vAB1-0003-Fix-ProcKill-lock-group-vs-procLatch-recycle-ra.patch
> Fix for the problem, proposed by the thread starter, rebased on current HEAD
> and test patch.
> The test passes after this step.
Deferring pgstat_reset_wait_event_storage() call in (3) enables the test 
in (1) to work once (2) is applied. Without this change, the test hangs. 
It might make sense to commit the test.

-- 
Best regards,
Vlad