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.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/4a1c0f3dde765c65e0ccb712c899df16986d09ad
Modified Files
--------------
src/bin/scripts/t/080_pg_isready.pl | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers