database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-08 22:02:03 +03:00
Code

Use a longer connection timeout in pg_isready test.

Browse Source 
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:
Tom Lane 2017-10-01 12:43:47 -04:00
parent 232c7cbcbb
commit 45ec8da100
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/bin/scripts/t/080_pg_isready.pl
View File

@ -12,4 +12,5 @@ command_fails(['pg_isready'], 'fails with no server running');
my $tempdir = tempdir; my $tempdir = tempdir;
start_test_server $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');