| From: | JoongHyuk Shin <sjh910805(at)gmail(dot)com> |
|---|---|
| To: | Vitaly Davydov <v(dot)davydov(at)postgrespro(dot)ru> |
| 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 05:30:20 |
| Message-ID: | CACSdjfMBDtxiFyA3eEVNJRQi1rufPGEjXOtAQ3qQkVc-P=187w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 2, 2026 at 12:57 AM Vitaly Davydov <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 ask because my patch at [1] reworks the same dispatch block in
ResolveRecoveryConflictWithBufferPin, and I plan to rebase it on top of
your rewrite, so I would like to time that.
Happy to help with testing if that is useful.
--
JH Shin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2026-08-04 05:44:53 | Re: [PATCH] Fix vacuum_delay_point happening inside lock |
| Previous Message | Christophe Pettus | 2026-08-04 05:25:52 | Re: [PATCH v3] Don't stop a `vacuumdb/reindex/ --all` on a connection failure |