summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Munro <tmunro@postgresql.org>2019-05-06 15:02:41 +1200
committerThomas Munro <tmunro@postgresql.org>2019-05-08 22:03:44 +1200
commit1f3bcb4972009c8af7b71d1526559475a248f77a (patch)
treeaa5a3d8923ffceb8e26b145c5e503829cc0d3d9f
parent2bc59f890100f9a90289f8ef10b9403294915ff8 (diff)
Probe only 127.0.0.1 when looking for ports on Unix.
Commit c0985099, later adjusted by commit 4ab02e81, probed 0.0.0.0 in addition to 127.0.0.1, for the benefit of Windows build farm animals. It isn't really useful on Unix systems, and turned out to be a bit inconvenient to users of some corporate firewall software. Switch back to probing just 127.0.0.1 on non-Windows systems. Back-patch to 9.6, like the earlier changes. Discussion: https://postgr.es/m/CA%2BhUKG%2B21EPwfgs4m%2BtqyRtbVqkOUvP8QQ8sWk9%2Bh55Aub1H3A%40mail.gmail.com
-rw-r--r--src/test/perl/PostgresNode.pm7
1 files changed, 4 insertions, 3 deletions
diff --git a/src/test/perl/PostgresNode.pm b/src/test/perl/PostgresNode.pm
index 7047d88fb62..7f5e3b5fecd 100644
--- a/src/test/perl/PostgresNode.pm
+++ b/src/test/perl/PostgresNode.pm
@@ -1044,14 +1044,15 @@ sub get_new_node
# This seems like a good idea on Unixen as well, even though we don't
# ask the postmaster to open a TCP port on Unix. On Non-Linux,
# non-Windows kernels, binding to 127.0.0.1/24 addresses other than
- # 127.0.0.1 fails with EADDRNOTAVAIL.
+ # 127.0.0.1 might fail with EADDRNOTAVAIL. Binding to 0.0.0.0 is
+ # unnecessary on non-Windows systems.
#
# XXX A port available now may become unavailable by the time we start
# the postmaster.
if ($found == 1)
{
- foreach my $addr (qw(127.0.0.1 0.0.0.0),
- $use_tcp ? qw(127.0.0.2 127.0.0.3) : ())
+ foreach my $addr (qw(127.0.0.1),
+ $use_tcp ? qw(127.0.0.2 127.0.0.3 0.0.0.0) : ())
{
can_bind($addr, $port) or $found = 0;
}