pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Michael Stone <mstone+postgres@mathom.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-performance@postgresql.org
Subject: Re: Best way to index IP data?
Date: Fri, 11 Jan 2008 16:27:05 -0500
Message-ID: <20080111212703.GU5294@mathom.us> (raw)
In-Reply-To: <24044.1200082058@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>
	<20080111162747.GT5294@mathom.us>
	<24044.1200082058@sss.pgh.pa.us>

On Fri, Jan 11, 2008 at 03:07:38PM -0500, Tom Lane wrote:
>Michael Stone <mstone+postgres@mathom.us> writes:
>> Well, a native IPv6 type would also be nice; inet is ridiculously 
>> bloated for both IPv4 *and* IPv6. 
>
>Nonsense.  3 bytes overhead on a 16-byte address is not "ridiculously
>bloated", especially if you want a netmask with it.

Big if, no? There's a very large set of users that *don't* want/need a 
netmask, which is why the topic keeps coming back. (Also, according to 
the docs, inet requires 24 bytes, which is 50% more than needed; is that 
not correct?)

Mike Stone



view thread (42+ messages)  latest in thread

Message-ID: <20080111212703.GU5294@mathom.us>
Permalink:  ../20080111212703.GU5294@mathom.us/
Also on:    postgresql.org/message-id/20080111212703.GU5294@mathom.us

 · 

reply
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: mstone+postgres@mathom.us, tgl@sss.pgh.pa.us
  Subject: Re: Best way to index IP data?
  In-Reply-To: <20080111212703.GU5294@mathom.us>

* 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