Thanks to all for the clarifications...
I'm looking at this form an application perspective...
as this would greatly enhance an IPAM database web application.
Sad there is no direct IP address sorting function like in MySQL (o;
cheers from .ch
richard
Am [DATE] schrieb "pgsql-sql-owner@postgresql.org im Auftrag von Tom Lane" <[ADDRESS]>:
>"David G. Johnston" <david.g.johnston@gmail.com> writes:
>> On Thu, Aug 6, 2015 at 10:02 AM, Adrian Klaver <adrian.klaver@aklaver.com>
>> wrote:
>>> " If the netmask is 32 and the address is IPv4, then the value does not
>>> indicate a subnet, only a single host."
>>>
>>> So it is behaving as documented.
>
>> This seems overly simplified given that "<<=" will indeed match two host
>> specifications.
>
>No, only one. There is no difference between '192.168.0.1'::inet and
>'192.168.0.1/32'::inet; they're the same value. The first notation
>is merely a shorthand for the second.
>
> regards, tom lane
>
>
>--
>Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-sql
