summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane2017-10-01 16:43:46 +0000
committerTom Lane2017-10-01 16:43:46 +0000
commit4a1c0f3dde765c65e0ccb712c899df16986d09ad (patch)
tree96d9fbfe6a9a8158981b9f13c8032b7f5849828a
parent655c938fb0aacde297d4c53daf97ff82a3b90fad (diff)
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.
-rw-r--r--src/bin/scripts/t/080_pg_isready.pl3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/bin/scripts/t/080_pg_isready.pl b/src/bin/scripts/t/080_pg_isready.pl
index d9830b5b3ad..d01804da371 100644
--- a/src/bin/scripts/t/080_pg_isready.pl
+++ b/src/bin/scripts/t/080_pg_isready.pl
@@ -15,4 +15,5 @@ my $node = get_new_node('main');
$node->init;
$node->start;
-$node->command_ok(['pg_isready'], 'succeeds with server running');
+# use a long timeout for the benefit of very slow buildfarm machines
+$node->command_ok([qw(pg_isready --timeout=60)], 'succeeds with server running');