Hi, On 2022-03-24 21:22:38 -0400, Tom Lane wrote: > serinus is 0-for-3 since then, and dragonet 0-for-4, so we can be pretty > confident that the failure is repeatable for them.
That's weird. They run on the same host, but otherwise they have very little in common. There's plenty other animals running on the same machine that didn't report errors. I copied serinus' configuration, ran the tests repeatedly, without reproducing the failure so far. Odd. Combined with the replslot failure I'd be prepared to think the machine has issues, except that the replslot thing triggered on other machines too. I looked through logs on the machine without finding anything indicating something odd. I turned on keep_error_builds for serinus. Hopefully that'll leave us with on-disk files to inspect. Greetings, Andres Freund
