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

From: Vitaly Davydov <v(dot)davydov(at)postgrespro(dot)ru>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Deadlock detector fails to activate on a hot standby replica
Date: 2026-06-09 16:18:51
Message-ID: 12324a50-95d3-4de4-bd89-b295924b35bb@postgrespro.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/5/26 14:58, Fujii Masao wrote:
> I've updated the patch based on these comments.
> Attached is the latest version.
>
> I removed the TAP test from this patch for now. I'll consider adding
> a test for this separately later.

Thank you again for your assistance. I agree with the code changes you've
proposed. I've updated 031_recovery_conflict.pl to include the deadlock
test, instead of creating a separate TAP test. The attached patch contains
these changes in its second commit. I've kept the patch version as v3 since
the original fix remains unchanged; this update only adds new tests.

With best regards,
Vitaly

Attachment Content-Type Size
v3-0001-Fix-deadlock-detector-activation-in-a-recovery-confl.patch text/x-patch 6.5 KB
v3-0002-Add-new-deadlock-conflict-test-in-031_recovery_confl.patch text/x-patch 4.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nisha Moond 2026-06-09 16:21:04 Re: Support EXCEPT for TABLES IN SCHEMA publications
Previous Message Ashutosh Bapat 2026-06-09 15:37:37 Re: (SQL/PGQ) cache lookup failed for label