diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-10-01 12:43:47 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-10-01 12:43:47 -0400 |
| commit | 10cb052404b431fc04958286849d97209fd097f7 (patch) | |
| tree | 5b0b3342a87013ce4f0471f30f94b65200ab62c2 /src | |
| parent | fb6de78a291b1871fd9a426b4d0f51230bac3259 (diff) | |
| download | postgresql-10cb052404b431fc04958286849d97209fd097f7.tar.gz postgresql-10cb052404b431fc04958286849d97209fd097f7.zip | |
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.
Diffstat (limited to 'src')
| -rw-r--r-- | src/bin/scripts/t/080_pg_isready.pl | 3 |
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 f432505d5cd..2ddb03d7c24 100644 --- a/src/bin/scripts/t/080_pg_isready.pl +++ b/src/bin/scripts/t/080_pg_isready.pl @@ -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'); |