On Tue, Jul 10, 2012 at 1:38 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
I think the ultimate question is, which ones of these should we include in core? We cannot drop the existing range_ops opclass, if only because that would break pg_upgrade. However, range_ops2 seems superior to it, so I think we should make that the default for new indexes.
Actually, I'm not fully satisfied with range_ops2. I expect it could be recommend for all cases, but actually it builds significantly slower and sometimes requires more pages for search. Likely, we have to write some recommedation in docs about which opclass to use in particular. Additionally, somebody could think GiST range indexing becoming tangled.
For SP-GiST, I don't think we need to include both quad and k-d tree implementations. They have quite similar characteristics, so IMHO we should just pick one. Which one would you prefer? Is there any difference in terms of code complexity between them? Looking at the performance test results, quad tree seems to be somewhat slower to build, but is faster to query. Based on that, I think we should pick the quad tree, query performance seems more important.
Agree, I think we should stay at quad tree implemetation.
------
With best regards,
Alexander Korotkov.
