Request a Demo
Home   >   mailing lists

Re: Deadlock detector fails to activate on a hot standby replica - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Deadlock detector fails to activate on a hot standby replica
Date
Msg-id CAHGQGwHejDzesOd_VFfwJdrWUqKbsvPf6cuTWJuuKs3t7tN+vQ@mail.gmail.com
Whole thread
In response to Re: Deadlock detector fails to activate on a hot standby replica  (Vitaly Davydov <v.davydov@postgrespro.ru>)
Responses Re: Deadlock detector fails to activate on a hot standby replica
List pgsql-hackers
Tree view 
On Thu, Jun 25, 2026 at 12:16 AM Vitaly Davydov
<v.davydov@postgrespro.ru> wrote:
>
> Dear Fujii Masao
>
> I've prepared patches of v6 for other majors. I hope, it will help.

Thanks for the patches for the stable branches!

I noticed that you added "buf_state &= ~BM_PIN_COUNT_WAITER;" to
BufferIsReadyForCleanup(). Could you tell me why that's necessary? My
understanding was that LockBufferForCleanup() is responsible for
clearing that flag, so I didn't think it was needed here.

But if it is necessary, I'd like to make the same change in master as
well, to keep the code as consistent as possible between master and
the stable branches.


> I will also think of a better approach for tap-test patch as well.

Thanks!

Regards,

--
Fujii Masao

pgsql-hackers by date:

Previous
From: Xuneng Zhou
Date:
Subject: Re: [PATCH] Prevent repeated deadlock-check signals in standby buffer pin waits
Next
From: Maxime Schoemans
Date:
Subject: Re: [PATCH] btree_gist: add cross-type integer operator support for GiST