| 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>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(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-22 03:29:38 |
| Message-ID: | CAGRkXqRiOtdshLHbpmq44W0FViJpmqEN4W2BxTbX0TYazPU7Wg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Manu,
Thanks for posting your patch, I have 3 thoughts.
1. I think it kills more than client writes. With a 2s timeout it also
killed
a session waiting for sync rep, and a COPY FROM STDIN client that
paused(in primary),
2. 061 failed 4 of 11 runs here. slow_reader stops reading before the
checksums launcher waits, so it gets killed.
3. shouldTerminateBarrierStraggler() recheck pss_barrierGeneration
under pss_mutex? because it can kill a new backend in the same slot.
Thanks,
Shihao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shihao zhong | 2026-10-22 03:39:15 | Re: [PG19] Indexes from 18 miss rows after pg_upgrade |
| Previous Message | shihao zhong | 2026-10-22 03:25:15 | Re: [PG19] Promotion hangs behind a backend blocked on a stuck client |