Re: [BUGS] Bug in create operator and/or initdb - Mailing list pgsql-hackers

From Greg Stark
Subject Re: [BUGS] Bug in create operator and/or initdb
Date
Msg-id 87651ese9f.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: [BUGS] Bug in create operator and/or initdb  ("John Hansen" <john@geeknet.com.au>)
Responses Re: [BUGS] Bug in create operator and/or initdb
List pgsql-hackers
"John Hansen" <john@geeknet.com.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
onfoo  (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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Rtree index method for inet/cidr
Next
From: John Hansen
Date:
Subject: Re: [BUGS] Bug in create operator and/or initdb