| 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-27 08:28:23 |
| Message-ID: | aharJ_sk7LosEIda@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 18, 2026 at 01:11:56PM +0300, Vlad Lesin wrote:
> Ok, I fixed the test to use distinct injection points for the lock group
> leader and follower.
I have spent a good portion of the day looking at 0002 and 0003,
simplified quite a few things around the comments and the reasons why
we are doing so (the code, these comments and the commit message had a
strong AI smell). And after convincing myself that the new logic is
sound I have applied and backpatched both patches.
The last part is the test, that I have not be able to get at yet. We
don't have injection points all the way down, but let's have coverage
on the branches where we can.
If you could send a rebase of the test on top of the current HEAD,
that should save me a few minutes..
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2026-05-27 08:34:37 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Fujii Masao | 2026-05-27 08:11:55 | Re: [PATCH] Release replication slot on error in SQL-callable slot functions |