| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | contrib/rtree_gist into core system? |
| Date: | 2005-06-26 14:03:46 |
| Message-ID: | 7966.1119794626@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I've mentioned this a couple times now, but here is an official
proposal:
I would like to move the contrib/rtree_gist functionality into the core
system before feature freeze. There are a couple arguments in favor:
* It's way past time GiST indexes got some regression testing in the
core build. rtree_gist is the only very plausible candidate for
near-term integration: I don't think tsearch2 is ready for that, and
the other GiST-using contrib modules are not of sufficient general
usefulness.
* 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.
Any objections?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-06-26 14:14:25 | Re: tsearch2 changes need backpatching? |
| Previous Message | Andrew Dunstan | 2005-06-26 13:54:08 | tsearch2 changes need backpatching? |