mirror of
https://github.com/postgres/postgres.git
synced 2025-06-08 22:02:03 +03:00
Use a longer connection timeout in pg_isready test.
Buildfarm members skink and sungazer have both recently failed this test, with symptoms indicating that the default 3-second timeout isn't quite enough for those very slow systems. There's no reason to be miserly with this timeout, so boost it to 60 seconds. Back-patch to all versions containing this test. That may be overkill, because the failure has only been observed in the v10 branch, but I don't feel like having to revisit this later.
This commit is contained in:
parent
232c7cbcbb
commit
45ec8da100
@ -12,4 +12,5 @@ command_fails(['pg_isready'], 'fails with no server running');
|
||||
my $tempdir = tempdir;
|
||||
start_test_server $tempdir;
|
||||
|
||||
command_ok(['pg_isready'], 'succeeds with server running');
|
||||
# use a long timeout for the benefit of very slow buildfarm machines
|
||||
command_ok([qw(pg_isready --timeout=60)], 'succeeds with server running');
|
||||
|
Loading…
x
Reference in New Issue
Block a user