From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 26 Sep 2023 23:02:17 +0000 (-0400)
Subject: doc:  clarify the behavior of unopenable listen_addresses
X-Git-Tag: REL_11_22~52
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=14e60252c441d39f244497b60ea60e69d52e39f8;p=thirdparty%2Fpostgresql.git

doc:  clarify the behavior of unopenable listen_addresses

Reported-by: Gurjeet Singh

Discussion: https://postgr.es/m/CABwTF4WYPD9ov-kcSq1+J+ZJ5wYDQLXquY6Lu2cvb-Y7pTpSGA@mail.gmail.com

Backpatch-through: 11
---

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index fbd53113401..c6c33d272b3 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -635,10 +635,15 @@ include_dir 'conf.d'
          <literal>::</literal> allows listening for all IPv6 addresses.
          If the list is empty, the server does not listen on any IP interface
          at all, in which case only Unix-domain sockets can be used to connect
-         to it.
+         to it.  If the list is not empty, the server will start if it
+         can listen on at least one TCP/IP address.  A warning will be
+         emitted for any TCP/IP address which cannot be opened.
          The default value is <systemitem class="systemname">localhost</systemitem>,
          which allows only local TCP/IP <quote>loopback</quote> connections to be
-         made.  While client authentication (<xref
+         made.
+       </para>
+       <para>
+         While client authentication (<xref
          linkend="client-authentication"/>) allows fine-grained control
          over who can access the server, <varname>listen_addresses</varname>
          controls which interfaces accept connection attempts, which