From: Steve Atkins <steve@blighty.com>
To: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Best way to index IP data?
Date: Thu, 10 Jan 2008 15:25:20 -0800
Message-ID: <DA6DE53A-2F69-46F3-8C96-B341ADCDDFAF@blighty.com> (raw)
In-Reply-To: <200801101614.54729.kevin@kevinkempterllc.com>
References: <200801101614.54729.kevin@kevinkempterllc.com>
On Jan 10, 2008, at 3:14 PM, Kevin Kempter wrote:
> Hi List;
>
> We'll be loading a table with begining & ending I.P.'s - the table
> will likely
> have upwards of 30million rows. Any thoughts on how to get the best
> performance out of queries that want to look for IP ranges or the
> use of
> between queries? Should these be modeled as integers?
http://pgfoundry.org/projects/ip4r/
That has the advantage over using integers, or the built-in inet type,
of being indexable for range and overlap queries.
Cheers,
Steve
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: steve@blighty.com
Subject: Re: Best way to index IP data?
In-Reply-To: <DA6DE53A-2F69-46F3-8C96-B341ADCDDFAF@blighty.com>
* 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