Re: [HACKERS] has anybody else used r-tree indexes in 6.5? - Mailing list pgsql-hackers

From Jeff Hoffmann
Subject Re: [HACKERS] has anybody else used r-tree indexes in 6.5?
Date
Msg-id 376E5D15.D37E782F@remapcorp.com
Whole thread Raw
In response to Re: [HACKERS] has anybody else used r-tree indexes in 6.5?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] has anybody else used r-tree indexes in 6.5?
List pgsql-hackers
Tom Lane wrote:
> 
> Jeff Hoffmann <jeff@remapcorp.com> writes:
> > has something changed with r-tree indexes in 6.5?
> > ERROR:  Operator 500 must have a restriction selectivity estimator to be
> > used in a btree index
> 
> What we have here is a big OOOPS.

i guess so.  the patch works fine, though, so no big deal.  i thought it
was weird that i hadn't heard it come up before since it didn't seem
like something i could have caused, but you never know.

> Apparently, none of the regression tests exercise rtree indexes at all,
> else we'd have known there was a problem.  Adding an rtree regression test
> seems to be strongly indicated as well...

i noticed this when i ran the regression tests and everything came out
ok, but forgot to mention it.  if i recall correctly, what's actually in
the geometry regression test is pretty weak.  i think it only really
tests some of the common cases, not all of the functions.  it's probably
not a high priority item, though, since, judging by how long it took for
this bug to surface, there aren't a lot of people using the geometry
functions/types.


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] 6.6 changes?
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] idea for 'module' support