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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
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 02:19:09
Message-ID: 4D84129D.6080002@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 03/18/2011 09:18 PM, Robert Haas wrote:
> 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.
>

It's already there, although I agree it's infelicitous.

cheers

andrew

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2011-03-19 02:22:22 Re: pgsql: Document the all-balls IPv6 address.
Previous Message Robert Haas 2011-03-19 02:12:43 pgsql: Fix possible "tuple concurrently updated" error in ALTER TABLE.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-03-19 02:21:46 Re: pg_last_xact_replay_timestamp meaning
Previous Message Robert Haas 2011-03-19 01:35:42 Re: pg_last_xact_replay_timestamp meaning