Message-ID: <fee569b3-d097-4a22-97a5-11268f0b954a@postgrespro.ru>
Date: Tue, 4 Aug 2026 14:16:24 +0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Deadlock detector fails to activate on a hot standby replica
To: JoongHyuk Shin <sjh910805@gmail.com>
Cc: Xuneng Zhou <xunengzhou@gmail.com>, Fujii Masao <masao.fujii@gmail.com>,
 pgsql-hackers@lists.postgresql.org
References: <44c24dcf-5710-410f-b1b6-d10b315f3d51@postgrespro.ru>
 <CAHGQGwHh5j=sG3AZh=HyuXtPM6cmymp6MJkRAMJcJUyN2qpHrQ@mail.gmail.com>
 <CAHGQGwF01sOHnh6_9yDWiAdBMNnGWsTpM89+8XeztMjV=xk+cw@mail.gmail.com>
 <279402b1-7f16-43fa-9dbf-df96a93245dd@postgrespro.ru>
 <CAHGQGwH325+6qz0g50XH-MrLe7xNH1d9snEqXevdCR3ACnLJoQ@mail.gmail.com>
 <16cdffd4-f06c-4957-9132-1849a719f3d4@postgrespro.ru>
 <CAHGQGwEykj-fTWSViwiSk=DKmb3tcE+zP_dm24+AoDZvar-HZw@mail.gmail.com>
 <790719db-f518-4300-8ce7-8f168cd0af84@postgrespro.ru>
 <CAHGQGwHejDzesOd_VFfwJdrWUqKbsvPf6cuTWJuuKs3t7tN+vQ@mail.gmail.com>
 <CABPTF7V2wgjqN6g99uxR_RjGYCLo07e8ogWWTyAqMfzAGg5j_g@mail.gmail.com>
 <7b1e8353-3d0a-48a1-bac6-2ac6ca91fbde@postgrespro.ru>
 <CABPTF7Xqx=hP7-TeMnXcA76V6Wd9ah3+KjucWVU6FqxS-WQmKg@mail.gmail.com>
 <CABPTF7WeTmUXcwXh9WsM8DnU+RB8Hw-U+EpZqkf1Lz8D2rBMaQ@mail.gmail.com>
 <5c50d50c-5a9c-4a9e-9592-183cf4de1c80@postgrespro.ru>
 <CACSdjfMBDtxiFyA3eEVNJRQi1rufPGEjXOtAQ3qQkVc-P=187w@mail.gmail.com>
Content-Language: en-US
From: Vitaly Davydov <v.davydov@postgrespro.ru>
In-Reply-To: 
 <CACSdjfMBDtxiFyA3eEVNJRQi1rufPGEjXOtAQ3qQkVc-P=187w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/fee569b3-d097-4a22-97a5-11268f0b954a%40postgrespro.ru>
Precedence: bulk

Hi JH Shin,

On 8/4/26 08:30, JoongHyuk Shin wrote:
 > On Thu, Jul 2, 2026 at 12:57 AM Vitaly Davydov <v.davydov@postgrespro.ru
 > <mailto:v.davydov@postgrespro.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@mail.ru