Skip site navigation (1) Skip section navigation (2)

Last chance to defend RTREE index access method

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Last chance to defend RTREE index access method
Date: 2005-11-05 21:47:41
Message-ID: 20465.1131227261@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
We previously discussed the idea of removing the rtree access method
in 8.2, on the grounds that GiST does everything rtree can do, only
better.  Now that GiST has WAL support and can do concurrent access,
it's pretty hard to see why anyone would want to use rtree instead;
and I haven't heard anyone volunteering to bring rtree up to speed.

We already have GiST opclasses in core that correspond to the core
rtree opclasses.  To arrange transparent migration of existing database
schemas, I believe it would be sufficient to put a kluge in DefineIndex
to substitute "gist" for "rtree" if it's asked to create an rtree index.

Any objections out there?

			regards, tom lane

pgsql-hackers by date

Next:From: Simon RiggsDate: 2005-11-06 08:45:58
Subject: Re: Reducing the overhead of NUMERIC data
Previous:From: Pavel StehuleDate: 2005-11-05 17:34:33
Subject: I can't get row type from tuple (SPI)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group