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
Ok, I see, but that's not really what I was wondering. My question is this:
SP-GiST partitions the space into non-overlapping sections. How can you store
polygons - which can overlap - in an SP-GiST index? And how does the compress
method help with that?
I believe if we found a way to index boxes then we will need a compress method
to build index over polygons.
BTW, we are working on investigation a index structure for box where 2d-box is
treated as 4d-point.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
