Re: Recent 027_streaming_regress.pl hangs
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Thomas Munro <thomas.munro@gmail.com>,
Alexander Lakhin <exclusion@gmail.com>,
Michael Paquier <michael@paquier.xyz>,
pgsql-hackers <pgsql-hackers@postgresql.org>,
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Date: 2024-03-26T04:54:54Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > On 2024-03-26 00:00:38 -0400, Tom Lane wrote: >> Are you sure it's not just that the total time to run the core >> regression tests has grown to a bit more than what the test timeout >> allows for? > You're right, that could be it - in a way at least, the issue is replay not > catching up within 180s, so it'd have to be the data volume growing, I think. > But it doesn't look like the regression volume meaningfully grew around that > time? No, but my impression is that the failure rate has been getting slowly worse for awhile now. > I guess I'll try to write a buildfarm database query to extract how long that > phase of the test took from all runs on my menagerie, not just the failing > one, and see if there's a visible trend. +1 regards, tom lane
Commits
-
Log more info when wait-for-catchup tests time out.
- e57296ed4867 17.0 landed
- 2aecbd752616 18.0 landed
-
Add a new slot sync worker to synchronize logical slots.
- 93db6cbda037 17.0 cited