Re: Why so few built-in range types? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Why so few built-in range types?
Date
Msg-id CA+TgmoZChY_K=stGN0aeMngKhJnOjS4kbD7+0C_9LK=krco4ww@mail.gmail.com
Whole thread Raw
In response to Re: Why so few built-in range types?  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Why so few built-in range types?  (Stephen Frost <sfrost@snowman.net>)
Re: Why so few built-in range types?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Wed, Nov 30, 2011 at 3:58 PM, Stephen Frost <sfrost@snowman.net> wrote:
> Erm, isn't there a contrib type that already does all that for you..?
> ip4r or whatever?  Just saying, if you're looking for that capability..

Oh, huh, good to know.  Still, I'm not sure why you need to load a
separate type to get this... there's no reason why the built-in CIDR
type couldn't support it.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Why so few built-in range types?
Next
From: "Kevin Grittner"
Date:
Subject: Re: FlexLocks