Re: Too-short timeouts in test code
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Noah Misch <noah@leadboat.com>
Cc: pgsql-hackers@postgresql.org
Date: 2018-12-09T02:14:12Z
Lists: pgsql-hackers
On Sat, Dec 08, 2018 at 04:16:01PM -0800, Noah Misch wrote:
> The 180s timeout in poll_query_until has been trouble-free since 2a0f89c
> introduced it two years ago. I plan to raise the timeouts in question to
> 180s, as attached.
That's annoying, thanks for tracking those down.
> @@ -72,7 +72,7 @@ my $endpos = $node_master->safe_psql('postgres',
> print "waiting to replay $endpos\n";
>
> my $stdout_recv = $node_master->pg_recvlogical_upto(
> - 'postgres', 'test_slot', $endpos, 10,
> + 'postgres', 'test_slot', $endpos, 180,
> 'include-xids' => '0',
> 'skip-empty-xacts' => '1');
Instead of allowing callers of pg_recvlogical_upto() to define the
timeout they want, perhaps it would be better to hardcode the timeout
limit within the routine?
--
Michael
Commits
-
Raise some timeouts to 180s, in test code.
- 752278e7748e 9.6.12 landed
- eff124233916 10.7 landed
- 73822b8c9750 11.2 landed
- 1db439ad4925 12.0 landed