Re: Summary: what to do about INET/CIDR - Mailing list pgsql-hackers

From Alex Pilosov
Subject Re: Summary: what to do about INET/CIDR
Date
Msg-id Pine.BSO.4.10.10010271833010.22890-100000@spider.pilosoft.com
Whole thread Raw
In response to Re: Summary: what to do about INET/CIDR  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Summary: what to do about INET/CIDR  ("Dominic J. Eidson" <sauron@the-infinite.org>)
List pgsql-hackers
On Fri, 27 Oct 2000, Tom Lane wrote:

> BTW, does it strike anyone else as peculiar that the host(),
> broadcast(), network(), and netmask() functions yield results
> of type text, rather than type inet?  Seems like it'd be considerably
> more useful if they returned values of type inet with masklen = 32
> (except for network(), which would keep the original masklen while
> coercing bits to its right to 0).
I absolutely agree, except for network(), which should return cidr.
(after all, this is the network).

As I mentioned in another email, should inet datatype really care whether
host part is all-ones or all-zeros and reject that? It would make sense to
me (10.0.0.0/8::inet is not a valid address, but 10.0.0.0/8::cidr is), but
it would break some people's scripts...

I'm talking here from a perspective of a network provider with P
knowledge...I'm sure Marc can chime in here...
-alex





pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Summary: what to do about INET/CIDR
Next
From: Tom Lane
Date:
Subject: Re: Re: [GENERAL] A rare error