| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Manu <manuelreyesbravo(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, Zhijie Hou <houzhijie22(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PG19] Promotion hangs behind a backend blocked on a stuck client |
| Date: | 2026-10-23 01:12:38 |
| Message-ID: | CAGRkXqT+S2TXwG_Hg+vDF5g5Ke62JcC3LisHEdVqDxq_SMJ2_Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Manu,
Thanks for the quick update and the gdb repro. I tested v2 and it
works for all three points.
One case is still stuck. A backend can block while it sends an
error. It holds interrupts then, so SIGTERM does nothing. v2 still
logs "terminating process". That can confuse users.
For the large value case, maybe add a send counter in PGPROC. If the
counter moves during the timeout, the client is slow but alive. I
have not tried this.
Thanks,
Shihao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shihao zhong | 2026-10-23 01:16:51 | Re: Trying out <stdatomic.h> |
| Previous Message | Chao Li | 2026-10-23 01:08:04 | Re: tablecmds: Deadlock caused by Attach Partition |