Skip site navigation (1) Skip section navigation (2)

Re: [BUGS] Bug in create operator and/or initdb

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: (view raw, whole thread or download thread mbox)
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 << '';
                                        QUERY PLAN                                        
 Index Scan using foo_foo_code on foo  (cost=0.00..34.56 rows=1695 width=229)
   Index Cond: ((foo_code > ''::cidr) AND (foo_code <= ''::cidr))
   Filter: (foo_code << ''::cidr)
(3 rows)


In response to


pgsql-hackers by date

Next:From: John HansenDate: 2005-01-30 23:18:23
Subject: Re: [BUGS] Bug in create operator and/or initdb
Previous:From: Tom LaneDate: 2005-01-30 22:50:23
Subject: Re: Rtree index method for inet/cidr

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group