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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Vlad Lesin <vladlesin(at)gmail(dot)com>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Fix ProcKill lock-group vs procLatch recycle race
Date: 2026-05-18 03:15:36
Message-ID: agqEWHYPwLXsp4Xp@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 15, 2026 at 03:29:30PM +0300, Vlad Lesin wrote:
> I moved the creation of injection_point_condition.h into a separate commit
> in 0001 patch.

Applied this one for now. I still need to look at the rest in
details.

> Additionally, I noticed that if several processes are waiting
> on the same injection point, only one of them will be awakened by a single
> injection_points_wakeup() call. I am not sure if this behavior is
> intentional; please let me know.

Yep, I recall that as being intentional, hence I don't feel that 0002
is a good thing to do, even worse doing so in the back-branches.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-05-18 03:20:14 PSQL - prevent describe listing tables that are already in listed schemas
Previous Message Chao Li 2026-05-18 02:25:16 Fix small issues of pg_restore_extended_stats()