Michael Paquier e5532f194c Fix failures with TAP tests of pg_ctl on Windows ... On Windows, all the hosts spawned by the TAP tests bind to 127.0.0.1. Hence, if there is a port conflict, starting a cluster would immediately fail. One of the test scripts of pg_ctl initializes a node without PostgresNode.pm, using the default port 5432. This could cause unexpected startup failures in the tests if an independent server was up and running on the same host (the reverse is also possible, though more unlikely). Fix this issue by assigning properly a free port to the node configured, in the same range used as for the other nodes part of the tests. Author: Michael Paquier Reviewed-by: Andrew Dunstan Discussion: https://postgr.es/m/20191202031444.GC1696@paquier.xyz Backpatch-through: 11		2019-12-03 13:01:06 +09:00
..
001_start_stop.pl	Fix failures with TAP tests of pg_ctl on Windows	2019-12-03 13:01:06 +09:00
002_status.pl	Updates to reflect that pg_ctl stop -m fast is the default	2017-01-13 21:25:36 -05:00
003_promote.pl	Post-PG 10 beta1 pgperltidy run	2017-05-17 19:01:23 -04:00
004_logrotate.pl	Initial pgperltidy run for v12.	2019-05-22 13:36:19 -04:00