From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-performance@postgresql.org
Subject: Re: Best way to index IP data?
Date: Fri, 11 Jan 2008 10:37:34 -0500
Message-ID: <20080111153734.GD5963@crankycanuck.ca> (raw)
In-Reply-To: <13179.1200064791@sss.pgh.pa.us>
References: <200801101614.54729.kevin@kevinkempterllc.com>
<DA6DE53A-2F69-46F3-8C96-B341ADCDDFAF@blighty.com>
<36e682920801101541o7626bbddj428617144240c554@mail.gmail.com>
<Pine.LNX.4.64.0801111025390.30762@localhost>
<13179.1200064791@sss.pgh.pa.us>
On Fri, Jan 11, 2008 at 10:19:51AM -0500, Tom Lane wrote:
> Given that the world is going to IPv6 in a few years whether you like it
> or not, that seems pretty darn short-sighted to me.
Indeed. Even ARIN has finally started to tell people that IPv4 is running
out. There are currently significant deployments of IPv6 in the
Asia-Pacific region. And it appears that Comcast is planning to move to
IPv6 for its own network deployment, which may mean that many U.S. homes
will have native v6 in the near future (the upshot of their plans aren't
actually clear to me yet, but if you're interested in some of what they're
telling people they're doing, look for Alain Durand's presentation to the
v6ops working group at the last IETF meeting).
> What would make sense IMHO is to adapt the improved indexing support in
> ip4r to work on the native inet/cidr types.
This seems like a good idea to me.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ajs@crankycanuck.ca
Subject: Re: Best way to index IP data?
In-Reply-To: <20080111153734.GD5963@crankycanuck.ca>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox