Hi,
On February 1, 2022 6:11:24 PM PST, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>Thomas Munro <thomas.munro@gmail.com> writes:
>> It looks like it's processing statements fairly consistently slowly
>> through the whole period. Each non-trivial statement takes a bit
>> under ~10ms, so it would make sense if by the time we've processed
>> ~2.5k lines we've clocked up 30 seconds and a VACUUM replay whacks us.
>
>This test is set up to time out after 30 seconds? We've long had
>an unofficial baseline that no timeouts under 180 seconds should
>be used in the buildfarm.
30s is the default value of the streaming replay conflict timeout. After that the startup process cancelled the session
runningpg_dump. So it's not an intentional timeout in the test.
It's not surprising that pg_dump takes 30s on that old a machine. But more than 2min still surprised me. Is that really
dobe expected?
- Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
