Re: [COMMITTERS] pgsql: Document the all-balls IPv6 address.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: [COMMITTERS] pgsql: Document the all-balls IPv6 address.
Date: 2011-03-19 03:00:19
Message-ID: 29251.1300503619@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Mar 18, 2011 at 10:19 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> On 03/18/2011 09:18 PM, Robert Haas wrote:
>>> "all balls" seems like a colloquialism best avoided in our documentation.

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

> I vote for taking it out. I think that could be interpreted as inappropriate.

IIRC, the pre-existing usage refers to time 00:00:00. It does not seem
especially useful to adopt the same terminology for network addresses;
that's more likely to confuse people than anything else.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Dave Page 2011-03-19 07:08:06 Re: pgsql: Document the all-balls IPv6 address.
Previous Message Robert Haas 2011-03-19 02:22:22 Re: pgsql: Document the all-balls IPv6 address.

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikhil Sontakke 2011-03-19 03:22:23 VACUUM FULL deadlock with backend startup
Previous Message Tom Lane 2011-03-19 02:40:53 Collations versus record-returning functions