Skip to content

Commit 14e6025

Browse files
committed
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
1 parent 71c27e8 commit 14e6025

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

doc/src/sgml/config.sgml

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -635,10 +635,15 @@ include_dir 'conf.d'
635635
<literal>::</literal> allows listening for all IPv6 addresses.
636636
If the list is empty, the server does not listen on any IP interface
637637
at all, in which case only Unix-domain sockets can be used to connect
638-
to it.
638+
to it. If the list is not empty, the server will start if it
639+
can listen on at least one TCP/IP address. A warning will be
640+
emitted for any TCP/IP address which cannot be opened.
639641
The default value is <systemitem class="systemname">localhost</systemitem>,
640642
which allows only local TCP/IP <quote>loopback</quote> connections to be
641-
made. While client authentication (<xref
643+
made.
644+
</para>
645+
<para>
646+
While client authentication (<xref
642647
linkend="client-authentication"/>) allows fine-grained control
643648
over who can access the server, <varname>listen_addresses</varname>
644649
controls which interfaces accept connection attempts, which

0 commit comments

Comments
 (0)