[postgis-tickets] [SCM] PostGIS branch master updated. 3.1.0rc1-432-g3b1a12e

git at osgeo.org git at osgeo.org
Wed Aug 25 12:17:46 PDT 2021


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "PostGIS".

The branch, master has been updated
       via  3b1a12e3e5ddabe31937cb4c673cfbb888020930 (commit)
      from  a9382ae7fdbcbe9666cad0c0303991f3049865b5 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 3b1a12e3e5ddabe31937cb4c673cfbb888020930
Author: Paul Ramsey <pramsey at cleverelephant.ca>
Date:   Wed Aug 25 12:17:42 2021 -0700

    Remove un-backed assertion that SPGIST indexes are best for highly overlapping data. Closes #4907

diff --git a/doc/using_postgis_dataman.xml b/doc/using_postgis_dataman.xml
index ef885cf..3bf80f6 100644
--- a/doc/using_postgis_dataman.xml
+++ b/doc/using_postgis_dataman.xml
@@ -2259,10 +2259,7 @@ CREATE INDEX [indexname] ON [tablename]
 
     <para>As it is the case for GiST indexes, SP-GiST indexes are lossy, in the
 		sense that they store the bounding box enclosing spatial objects.
-		SP-GiST indexes can be considered as an alternative to GiST indexes. The
-		performance tests reveal that SP-GiST indexes are especially beneficial
-		when there are many overlapping objects, that is, with so-called
-		“spaghetti data”.</para>
+		SP-GiST indexes can be considered as an alternative to GiST indexes.</para>
 
 		<para>Once a GIS data table exceeds a few thousand rows, an SP-GiST index
 		may be used to speed up spatial searches of the data. The syntax for

-----------------------------------------------------------------------

Summary of changes:
 doc/using_postgis_dataman.xml | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)


hooks/post-receive
-- 
PostGIS


More information about the postgis-tickets mailing list