Opened 4 years ago

Closed 3 years ago

#4907 closed defect (fixed)

Documentation - are SP-GiST indexes really better for overlapping bounding boxes?

Reported by: Laurenz Albe Owned by: pramsey
Priority: medium Milestone: PostGIS 3.2.0
Component: documentation Version: master
Keywords: documentation spgist Cc:

Description

The documentation claims that

The performance tests reveal that SP-GiST indexes are especially beneficial when there are many overlapping objects, that is, with so-called “spaghetti data”.

That is counter-intuitive, given that SP-GiST indexes use disjoint bounding boxes, and Paul Ramsey's recent blog post confirms that:

When there is less overlap, then SPGIST will out-perform GIST.

Perhaps the documentation should be fixed.

Change History (3)

comment:1 by Laurenz Albe, 4 years ago

Component: postgisdocumentation
Keywords: documentation spgist added
Milestone: PostGIS 3.1.2PostGIS 3.2.0
Owner: changed from pramsey to robe
Version: 2.5.xmaster

comment:2 by robe, 4 years ago

Owner: changed from robe to pramsey

I think the Spgist spatial index was added by MobilityDB group and presumably the description of it's use was probably added by them. I personally haven't noticed much of a difference between spgist and gist indexes for most PostGIS cases. Perhaps pramsey can update the docs accordingly since I have no such metric that they are better.

comment:3 by Paul Ramsey <pramsey@…>, 3 years ago

Resolution: fixed
Status: newclosed

In 3b1a12e/git:

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

Note: See TracTickets for help on using tickets.