> On 1 Nov 2024, at 00:25, Thom Brown <t...@linux.com> wrote:
>
> 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()".
>
Currently I do not see how this wait can result in a deadlock.
But I did observe standby in a pathological sequential scan encountering recent
multixact again and again (new each time).
I hope this situation will be alleviated by recent cahnges - now there is not a
millisecond wait, but hopefully smaller amount of time.
In v17 we also added injection point test which reproduces reading very recent
multixact. If there is a deadlock I hope buildfarm will show it to us.
Best regards, Andrey Borodin.
