diff options
| author | Michael Paquier <michael@paquier.xyz> | 2019-12-03 13:01:40 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2019-12-03 13:01:40 +0900 |
| commit | ef30975b49702f9f8aaed7b1cd8f78470ed1b22d (patch) | |
| tree | 731173089fdef5dacccae3b3d5593a5d127d5756 /src/backend/access/gist/gistget.c | |
| parent | b154d70f743039452f2cadee9566d754e79e3653 (diff) | |
| download | postgresql-ef30975b49702f9f8aaed7b1cd8f78470ed1b22d.tar.gz postgresql-ef30975b49702f9f8aaed7b1cd8f78470ed1b22d.zip | |
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
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions