Gilberto Castillo Mart�nez wrote:
>
>
> El jue, 10-03-2011 a las 15:33 -0500, Bruce Momjian escribi?:
> > Dyonisius Visser wrote:
> > > On 10 March 2011 21:03, Bruce Momjian <bruce@momjian.us> wrote:
> > >
> > > > OK, let's skip documenting this then. ?They can already do this via
> > > > pg_hba.conf.
> > >
> > > Restricting access via pg_hba.conf is something else than listening
> > > (or not) on sockets...
> > >
> > > FYI, the listen_addresses is basically the same as sshd's ListenAddress.
> >
> > Yes, listen_addresses prevents anyone from even binding to the address.
>
> I keep thinking you should put that information somewhere accessible
> comun.
Attached doc patch applied.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 8e27f73..0c682c8 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -324,7 +324,9 @@ SET ENABLE_SEQSCAN TO OFF;
to listen for connections from client applications.
The value takes the form of a comma-separated list of host names
and/or numeric IP addresses. The special entry <literal>*</>
- corresponds to all available IP interfaces.
+ corresponds to all available IP interfaces. The entry
+ <literal>0.0.0.0</> allows listening for all IPv4 addresses and
+ <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.