Re: Adding ip4r to Postgresql core? - Mailing list pgsql-general

From Tom Lane
Subject Re: Adding ip4r to Postgresql core?
Date
Msg-id 4511.1375937082@sss.pgh.pa.us
Whole thread Raw
In response to Re: Adding ip4r to Postgresql core?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Adding ip4r to Postgresql core?  (Chris Travers <chris.travers@gmail.com>)
List pgsql-general
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Tom Lane wrote:
>> That's been proposed before, and rejected before, on the grounds that
>> since it doesn't support IPv6 its days are numbered.

> Actually, that's not true.

Ah, my information is obsolete.

>  Quoting from the linked readme file,
> : IP4R therefore supports six distinct data types:
> :   ip4   - a single IPv4 address
> :   ip4r  - an arbitrary range of IPv4 addresses
> :   ip6   - a single IPv6 address
> :   ip6r  - an arbitrary range of IPv6 addresses
> :   ipaddress  - a single IPv4 or IPv6 address
> :   iprange    - an arbitrary range of IPv4 or IPv6 addresses

So the obvious question today is whether this isn't duplicative of the
range datatype stuff.  IOW, why wouldn't we be better off to invent
inetrange and call it good?

            regards, tom lane


pgsql-general by date:

Previous
From: Sameer Thakur
Date:
Subject: Re: Self referencing composite datatype
Next
From: Sergey Konoplev
Date:
Subject: Re: How to avoid Force Autovacuum