Horton

Re: Recent 027_streaming_regress.pl hangs

Thomas Munro <thomas.munro@gmail.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>, Alexander Lakhin <exclusion@gmail.com>, Michael Paquier <michael@paquier.xyz>, pgsql-hackers <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Date: 2024-07-25T22:10:29Z
Lists: pgsql-hackers 
On Fri, Jul 26, 2024 at 9:14 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Based on this, it seems fairly likely that crake is simply timing out
> as a consequence of intermittent heavy background activity.

Would it be better to keep going as long as progress is being made?
I.e. time out only when the relevant LSN stops advancing for N
seconds?  Or something like that...

Commits

  1. Log more info when wait-for-catchup tests time out.

  2. Add a new slot sync worker to synchronize logical slots.