Re: pgsql: Document the all-balls IPv6 address.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Document the all-balls IPv6 address.
Date: 2011-03-19 01:18:13
Message-ID: AANLkTi==Eq5N3F0AQXmrEqhcWxSZM0sE5ChEiVKA4_JD@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Fri, Mar 18, 2011 at 6:56 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> + <literal>0.0.0.0/0</literal> (<quote>all balls</>) represents all
> +       IPv4 addresses, and <literal>::</literal> represents
> +       all IPv6 addresses.
>
> Umm, isn't there a missing netmask there? The IPv6 analog of 0.0.0.0/0 is
> surely ::/0 (or I would usually write it ::0/0).

"all balls" seems like a colloquialism best avoided in our documentation.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2011-03-19 01:23:35 Re: pgsql: Remove ancient -X options to pg_dump, pg_dumpall, pg_restore.
Previous Message Tom Lane 2011-03-19 01:12:52 Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-03-19 01:20:43 Re: pg_ctl restart - behaviour based on wrong instance
Previous Message Tom Lane 2011-03-19 01:12:52 Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.