| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: contrib/rtree_gist into core system? |
| Date: | 2005-06-27 04:44:48 |
| Message-ID: | 27379.1119847488@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> * With the recent WAL-ization and hoped-for concurrency fixes, GiST
>> is definitely superior to R-tree for practical use. I don't see the
>> percentage in continuing to maintain the R-tree code indefinitely.
>> By integrating the opclasses needed to replace R-tree, we can start
>> down the path to deprecating and eventually removing R-tree.
> I think we still have a serious problem with multicolumn indexes. As they
> stand they're basically only indexes on the first column. The later columns
> are not used to determine page splits.
R-tree doesn't do multicolumn at all, so this is is hardly an argument
for keeping it, is it?
> Also, isn't rtree still substantially faster than gist?
Not according to contrib/rtree_gist/bench/, though I admit I have not
bothered to reproduce the experiment.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2005-06-27 04:49:20 | Re: contrib/rtree_gist into core system? |
| Previous Message | Greg Stark | 2005-06-27 04:34:34 | Re: contrib/rtree_gist into core system? |