From: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: compress method for spgist - 2 |
Date: | 2015-03-04 16:58:33 |
Message-ID: | CACowWR2LhVi4JHEVV=PYzLSyBfnpMd5+bhr2R8t5vzs0o79Ndw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 25, 2015 at 6:13 AM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Marco Nenciarini | 2015-03-04 16:59:58 | Re: File based Incremental backup v8 |
Previous Message | Mike Rylander | 2015-03-04 16:48:32 | Re: xpath changes in the recent back branches |