[postgis-users] Improvement suggestion

[Darafei "Komяpa" Praliaskouski]

If you are managing large geometries, splitting them off into "geometry
table" with non-uniquie ID and subdivided parts sometimes helps.
You want to build a tree on top of your geometry internals to make it all
fast, one way to do that is to make sure the internal parts of geometry are
available for indexing in GiST, via ST_Subdivide.

Other beautiful way would be to hide this all behind the scenes in PostGIS
itself and making ST_Intersection and ST_Intersects optimize the cases you
mentioned internally, caching some kind of tree internally, probably in the
geometry itself.

On Mon, Dec 3, 2018 at 11:43 PM Paul van der Linden <
paul.doskabouter at gmail.com> wrote:

> No, didn't do that.
> Don't think it's going to improve readability of the query to be honest
> _______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users



-- 
Darafei Praliaskouski
Support me: http://patreon.com/komzpa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20181204/2cbad4c6/attachment.html>