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

From Vitaly Davydov
Subject Re: Deadlock detector fails to activate on a hot standby replica
Date
Msg-id 7b1e8353-3d0a-48a1-bac6-2ac6ca91fbde@postgrespro.ru
Whole thread
In response to Re: Deadlock detector fails to activate on a hot standby replica  (Xuneng Zhou <xunengzhou@gmail.com>)
Responses Re: Deadlock detector fails to activate on a hot standby replica
List pgsql-hackers
Hi Fujii-san, Xuneng Zhou,

 > 1) It looks that this patch is doing some refactoring around
 > LockBufferForCleanup. The part being touched seems flaky itself on
 > HEAD, should we fix the issue in the buffer side first? [1]

Thank you for mentioning it. It seems, there is a conflict with
the another patch due to the introduction of RegisterPinCountWaiter
function, that can not be resolved automatically. I'm ok to wait for
the conflicting fix to be released. It seems, our patch should be
reconsidered after the conflicting patch release.

 > 2) buf_state &= ~BM_PIN_COUNT_WAITER in stable versions seems not
 > necessary to me as LockBufferForCleanup will handle the clearing for
 > us.

It seems it was my mistake when I resolved conflicts when cherry-picking
the changes from other branches. I removed this line in my recent v 6.1
attached patches. Thank you for catching it.

With best regards,
Vitaly
Attachment

pgsql-hackers by date:

Previous
From: Chao Li
Date:
Subject: Clear base backup progress reporting on error
Next
From: "cca5507"
Date:
Subject: Re: Handle concurrent drop when doing whole database vacuum