Re: compress method for spgist - 2
Paul Ramsey <pramsey@cleverelephant.ca>
From: Paul Ramsey <pramsey@cleverelephant.ca>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
Cc: Teodor Sigaev <teodor@sigaev.ru>,
Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2015-03-04T16:58:33Z
Lists: pgsql-hackers
On Wed, Feb 25, 2015 at 6:13 AM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote: > In the original post on this, you mentioned that the PostGIS guys planned to > use this to store polygons, as bounding boxes > (http://www.postgresql.org/message-id/5447B3FF.2080406@sigaev.ru). Any idea > how would that work? Poorly, by hanging boxes that straddled dividing lines off the parent node in a big linear list. The hope would be that the case was sufficiently rare compared to the overall volume of data, to not be an issue. Oddly enough this big hammer has worked in other implementations at least passable well (https://github.com/mapserver/mapserver/blob/branch-7-0/maptree.c#L261) P.
Commits
-
Doc: remove duplicate poly_ops row from SP-GiST opclass table.
- d3b851e9a3c9 11.0 landed
-
Add polygon opclass for SP-GiST
- ff963b393ca9 11.0 landed