From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [BUGS] Bug in create operator and/or initdb |
Date: | 2005-01-30 23:12:12 |
Message-ID: | 87651ese9f.fsf@stark.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"John Hansen" <john(at)geeknet(dot)com(dot)au> writes:
> I wouldn't think so, anyone I've spoken with has come up with other ways of
> managing that kind of info, because of, as you mentioned, it's lack of
> proper index methods.
On the contrary I'm using it for something that isn't really what it was
designed for precisely *because* of the index methods. What index access
methods are you looking for that are lacking?
db=> explain select * from foo where foo_code << '4.0.0.0/8';
QUERY PLAN
------------------------------------------------------------------------------------------
Index Scan using foo_foo_code on foo (cost=0.00..34.56 rows=1695 width=229)
Index Cond: ((foo_code > '4.0.0.0/8'::cidr) AND (foo_code <= '4.255.255.255'::cidr))
Filter: (foo_code << '4.0.0.0/8'::cidr)
(3 rows)
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | John Hansen | 2005-01-30 23:18:23 | Re: [BUGS] Bug in create operator and/or initdb |
Previous Message | Tom Lane | 2005-01-30 22:50:23 | Re: Rtree index method for inet/cidr |