| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Xuneng Zhou <xunengzhou(at)gmail(dot)com> |
| Cc: | Vitaly Davydov <vitprof(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, JoongHyuk Shin <sjh910805(at)gmail(dot)com> |
| Subject: | Re: Deadlock detector fails to activate on a hot standby replica |
| Date: | 2026-10-28 02:16:47 |
| Message-ID: | CAGRkXqRswzdS+WAQO_VoKi4zk5qso1Cop7x_2t53aq1QUuFEyg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Xuneng,
Thanks for v10 and for finding the lock case. I tested it and have
a few notes.
1. I am able to reproduce the case with your code and when
it passed deadlock_timeout. And your V10 is able to cancel the
deadlocked query.
2. V10 leaves the case where the delay has already passed as it was,
one wait with no timeout. So the problem in CF 6445 [1] is still
there.
I think this patch is LGTM.
[1] https://commitfest.postgresql.org/patch/6445/
Thanks,
Shihao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2026-10-28 02:23:43 | Re: bug: query returns different result with and without memoization. |
| Previous Message | Sho Ito | 2026-10-28 02:00:16 | Re: [PATCH] Fix whole-row type errors in postgres_fdw UPDATE joins |