Re: Deadlock detector fails to activate on a hot standby replica

From: Vitaly Davydov <v(dot)davydov(at)postgrespro(dot)ru>
To: JoongHyuk Shin <sjh910805(at)gmail(dot)com>
Cc: Xuneng Zhou <xunengzhou(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Deadlock detector fails to activate on a hot standby replica
Date: 2026-08-04 11:16:24
Message-ID: fee569b3-d097-4a22-97a5-11268f0b954a@postgrespro.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi JH Shin,

On 8/4/26 08:30, JoongHyuk Shin wrote:
> On Thu, Jul 2, 2026 at 12:57 AM Vitaly Davydov <v(dot)davydov(at)postgrespro(dot)ru
> <mailto:v(dot)davydov(at)postgrespro(dot)ru>> wrote:
>> It seems, the patch should be completely rewritten. I will try to
>> prepare a new patch version.
>
> Hi Vitaly,
>
> Any update on the new version you mentioned in your last message?

I can't give you an exact time right now because of the issues highlighted
in the last review that need to be elaborated on. Sorry, I've just started
looking at it again. It might take a week or two. If your patch is ready for
commit, please go ahead with it. As I see it, the main change in your patch
avoids periodic message logging by passing the log_recovery_conflict variable
from the caller. Once your changes are committed, I don't foresee any problems
merging them into my patch.

Vitaly Davydov
vitcpp(at)mail(dot)ru

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2026-08-04 11:16:48 Re: [PATCH] Release replication slot on error in SQL-callable slot functions
Previous Message Hannu Krosing 2026-08-04 11:15:30 Re: WAL compression setting after PostgreSQL LZ4 default change