Re: ipv4 data type does not allow to use % assubnet mask delimiter

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Andrus <kobruleht2(at)hot(dot)ee>, PostgreSQL - General <pgsql-general(at)postgresql(dot)org>
Subject: Re: ipv4 data type does not allow to use % assubnet mask delimiter
Date: 2010-11-16 20:38:51
Message-ID: 5261.1289939931@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On mn, 2010-11-15 at 11:06 +0200, Andrus wrote:
>>> Possibly someday the standard will actually standardize the things,
>>> and then maybe we can work with them usefully ...

>> From http://tools.ietf.org/html/rfc4007#section-11.2
>> so this is clearly standardized.

> Send a patch please.

Please note where the above-cited reference says

The precise format and semantics of additional strings is
implementation dependent.

The paragraphs following that get even vaguer. In particular, while
the standard clearly envisions that non-numeric zone ids should be
equivalent to some numeric zone id, the mapping between them is not
specified. Hence it's impossible to determine validity, let alone
test equality, except by reference to some specific implementation's
behavior.

I really think this is something we shouldn't touch, at least not
till standard practices emerge.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2010-11-16 20:39:37 Re: How to select a postgresql table inside Oracle
Previous Message Vick Khera 2010-11-16 20:36:41 Re: AfterTriggerSaveEvent() called outside of query