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

> What we have here is a big OOOPS.
> The right fix would be to put in an appropriate selectivity estimator,
> but we can't do that as a 6.5.* patch because changing pg_operator
> requires an initdb. It will have to wait for 6.6. (One of my to-do
> items for 6.6 was to rewrite the selectivity estimators anyway, so I'll
> see what I can do.)

Uh, I think we *should* do it as a patch, just not one applied to the
cvs tree for the v.6.5.x branch. Let's apply it to the main cvs branch
once we do the split, and Jeff can use a snapshot at that time (since
it will strongly resemble v6.5 and since he wants the capability).

In the meantime, can you/we develop a set of patches for Jeff to use?
Once we have them, we can post them into
ftp://postgresql.org/pub/patches, which probably needs to be cleaned
out from the v6.4.x period.

Let me know if I can help with any of this...

> In the meantime, I think the only possible patch is
> to disable the error check in btreesel and have it return a default
> selectivity estimate instead of complaining. Drat.

... and let's use this solution for the v6.5.x branch, once it comes
into being.

- Thomas

--
Thomas Lockhart lockhart(at)alumni(dot)caltech(dot)edu
South Pasadena, California