pgsql: Use a longer connection timeout in pg_isready test.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use a longer connection timeout in pg_isready test.
Date: 2017-10-01 16:44:06
Message-ID: E1dyhLa-0003yk-DL@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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
------
REL9_4_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/45ec8da100a1adcbc792025db59d3009d78da02d

Modified Files
--------------
src/bin/scripts/t/080_pg_isready.pl | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-10-01 17:32:34 pgsql: Update v10 release notes, and set the official release date.
Previous Message Alvaro Herrera 2017-10-01 13:31:01 Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple