Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit8c7a8e1

Browse files
committed
Probe only 127.0.0.1 when looking for ports on Unix.
Commitc098509, later adjusted by commit4ab02e8, probed 0.0.0.0in addition to 127.0.0.1, for the benefit of Windows build farmanimals. It isn't really useful on Unix systems, and turned out tobe 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
1 parent9e078fe commit8c7a8e1

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

‎src/test/perl/PostgresNode.pm

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -991,14 +991,15 @@ sub get_new_node
991991
# This seems like a good idea on Unixen as well, even though we don't
992992
# ask the postmaster to open a TCP port on Unix. On Non-Linux,
993993
# non-Windows kernels, binding to 127.0.0.1/24 addresses other than
994-
# 127.0.0.1 fails with EADDRNOTAVAIL.
994+
# 127.0.0.1 might fail with EADDRNOTAVAIL. Binding to 0.0.0.0 is
995+
# unnecessary on non-Windows systems.
995996
#
996997
# XXX A port available now may become unavailable by the time we start
997998
# the postmaster.
998999
if ($found == 1)
9991000
{
1000-
foreachmy$addr (qw(127.0.0.1 0.0.0.0),
1001-
$use_tcp ?qw(127.0.0.2 127.0.0.3) : ())
1001+
foreachmy$addr (qw(127.0.0.1),
1002+
$use_tcp ?qw(127.0.0.2 127.0.0.3 0.0.0.0) : ())
10021003
{
10031004
can_bind($addr,$port)or$found = 0;
10041005
}

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp