From: | Jeff Hoffmann <jeff(at)remapcorp(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] has anybody else used r-tree indexes in 6.5? |
Date: | 1999-06-21 15:41:09 |
Message-ID: | 376E5D15.D37E782F@remapcorp.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> Jeff Hoffmann <jeff(at)remapcorp(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 1999-06-21 16:21:43 | Re: [HACKERS] idea for 'module' support |
Previous Message | Bruce Momjian | 1999-06-21 15:08:39 | Re: [HACKERS] 6.6 changes? |