postgresql/src/bin/scripts/t
Tom Lane 4a1c0f3dde 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.
2017-10-01 12:43:46 -04:00
..
010_clusterdb.pl Post-PG 10 beta1 pgperltidy run 2017-05-17 19:01:23 -04:00
011_clusterdb_all.pl PostgresNode: Add names to nodes 2016-01-20 14:13:11 -03:00
020_createdb.pl PostgresNode: Add names to nodes 2016-01-20 14:13:11 -03:00
040_createuser.pl Establish conventions about global object names used in regression tests. 2016-07-17 18:42:43 -04:00
050_dropdb.pl Rework PostgresNode's psql method 2016-03-03 17:58:30 -03:00
070_dropuser.pl Establish conventions about global object names used in regression tests. 2016-07-17 18:42:43 -04:00
080_pg_isready.pl Use a longer connection timeout in pg_isready test. 2017-10-01 12:43:46 -04:00
090_reindexdb.pl Post-PG 10 beta1 pgperltidy run 2017-05-17 19:01:23 -04:00
091_reindexdb_all.pl PostgresNode: Add names to nodes 2016-01-20 14:13:11 -03:00
100_vacuumdb.pl Post-PG 10 beta1 pgperltidy run 2017-05-17 19:01:23 -04:00
101_vacuumdb_all.pl PostgresNode: Add names to nodes 2016-01-20 14:13:11 -03:00
102_vacuumdb_stages.pl PostgresNode: Add names to nodes 2016-01-20 14:13:11 -03:00
200_connstr.pl Post-PG 10 beta1 pgperltidy run 2017-05-17 19:01:23 -04:00