From: Pomarede Nicolas <npomarede@corp.free.fr>
To: pgsql-performance@postgresql.org
Subject: Re: Best way to index IP data?
Date: Fri, 11 Jan 2008 10:31:26 +0100 (CET)
Message-ID: <Pine.LNX.4.64.0801111025390.30762@localhost> (raw)
In-Reply-To: <36e682920801101541o7626bbddj428617144240c554@mail.gmail.com>
References: <200801101614.54729.kevin@kevinkempterllc.com>
<DA6DE53A-2F69-46F3-8C96-B341ADCDDFAF@blighty.com>
<36e682920801101541o7626bbddj428617144240c554@mail.gmail.com>
On Thu, 10 Jan 2008, Jonah H. Harris wrote:
> On Jan 10, 2008 6:25 PM, Steve Atkins <steve@blighty.com> wrote:
>> 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.
>
> Agreed. ip4r is da bomb.
Hello to all,
I also have to store a lot of IP v4 addresses, and I think the internal
inet type is somewhat overkill for that, since it always require 8 bytes,
even if you don't need to store a netmask.
When storing millions of IP add, this means MB of space used for nothing
in that case.
As ip4r seems to work very well with postgresql, is there a possibility to
see it merged in postgresql, to have a native 4 bytes IPv4 address date
type ?
Nicolas
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: npomarede@corp.free.fr
Subject: Re: Best way to index IP data?
In-Reply-To: <Pine.LNX.4.64.0801111025390.30762@localhost>
* 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