> On 28 Jun 2025, at 00:37, Andrey Borodin <x4...@yandex-team.ru> wrote: > > Indeed.
After some experiments I could get unstable repro on my machine. I've added some logging and that's what I've found: 2025-06-28 23:03:40.598 +05 [40887] 006_MultiXact_standby.pl WARNING: Timed out: nextMXact 415832 tmpMXact 415827 pageno 203 prev_pageno 203 entryno 83 offptr[1] 831655 offptr[0] 0 offptr[-1] 831651 We are reading 415827-1 Multi, while 415827 is not filled yet. But we are holding a buffer that prevents next Multi to be filled in. This seems like a recovery conflict. I'm somewhat surprized with 415827+1 is already filled in... Can you please try your reproduction with applied patch? This seems to be fixing issue for me. Best regards, Andrey Borodin.
v4-0001-Make-next-multixact-sleep-timed-with-a-recovery-c.patch
Description: Binary data
