Why aren’t PostgreSQL R-Tree indexes supported?

From PostGIS Manual: Early versions of PostGIS used the PostgreSQL R-Tree indexes. However, PostgreSQL R-Trees have been completely discarded since version 0.6, and spatial indexing is provided with an R-Tree-over-GiST scheme.
Our tests have shown search speed for native R-Tree and GiST to be comparable. Native PostgreSQL R-Trees have two limitations which make them undesirable for use with GIS features (note that these limitations are due to the current PostgreSQL native R-Tree implementation, not the R-Tree concept in general):

1. R-Tree indexes in PostgreSQL cannot handle features which are larger than 8K in size. GiST indexes can, using the “lossy” trick of substituting the bounding box for the feature itself.
2. R-Tree indexes in PostgreSQL are not “null safe”, so building an index on a geometry column which contains null geometries will fail.

Related posts:

• PostGIS 1.5.0 Release
• 将网站数据库系统从MySQL转向 PostgreSQL
• Install PostgreSQL in Ubuntu Linux
• Postgis, MapServer and OpenLayers
• PostGIS 1.3.4 支持GeoJSON格式输出