| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, Andrew Borodin <amborodin86(at)gmail(dot)com>, Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Gilles Darold <gilles(at)darold(dot)net>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: MultiXact\SLRU buffers configuration |
| Date: | 2024-10-31 19:25:11 |
| Message-ID: | CAA-aLv7-fs32r7v8znJ=uPPtQNqZ9_sH2REn=cu1pyEQ=tuEhw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 31 Oct 2024, 17:33 Andrey M. Borodin, <x4mmm(at)yandex-team(dot)ru> wrote:
>
>
> > On 31 Oct 2024, at 17:29, Thom Brown <thom(at)linux(dot)com> wrote:
> >
> > On Thu, 31 Oct 2024 at 10:47, Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru>
> wrote:
> >>
> >>
> >>
> >>> On 29 Oct 2024, at 21:45, Thom Brown <thom(at)linux(dot)com> wrote:
> >>>
> >>> It clearly checks for interrupts, but when I saw this issue happen, it
> >>> wasn't interruptible.
> >>
> >> Perhaps, that was different multixacts?
> >> When I was observing this pathology on Standby, it was a stream of
> different reads encountering different multis.
> >>
> >> Either way startup can cancel locking process on it's own. Or is it the
> case that cancel was not enough, did you actually need termination, not
> cancel?
> >
> > Termination didn't work on either of the processes.
>
> How did you force the process to actually terminate?
> Did you observe repeated read of the same multixact?
> Was offending process holding any locks while waiting?
>
Unfortunately I didn't gather much information when it was occuring, and
prioritised getting rid of the process blocking replay. I just attached gdb
to it, got a backtrace and then "print ProcessInterrupts()".
Thom
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2024-10-31 19:41:27 | Re: RFC: Extension Packaging & Lookup |
| Previous Message | Nathan Bossart | 2024-10-31 19:21:24 | Re: Popcount optimization using AVX512 |