[postgis-devel] PostGIS 3 thought experiment
Brian M Hamlin
maplabs at light42.com
Wed Jan 17 10:09:28 PST 2018
initial thoughts :
* a dedicated schema is good, but not the name 'postgis'
* cached validity flag(s) for polygons
* a chance to update all build requirements.. "clean slate"
general:
* how to tease/pull/force more parallelism, really
trivial example.. while pulling the OSM polys for buildings,
I routinely make a POINT version with PtOnSurface.
With 4.6 million polys, making a POINT out of each..
one core used on a 32 core beast..
* Search Engine? fast, fast, fast cached results..
if things are invariant,
look for it, use the RAM, pre-calc or saved.. something..
best regards from Berkeley --Brian
On Wed, 17 Jan 2018 09:44:23 -0800, Paul Ramsey
wrote:
What else is on everyone's wish list? Preferably things you'd do if
you didn't think everyone would shoot you down for being too
disruptive.
https://trac.osgeo.org/postgis/wiki/PostGIS3
* Break out a postgis_raster extension with a postgis dependency, so
raster support becomes optional.
* Require installation in a 'postgis' schema, always and for ever
* Yet another serialization, this time changing to use external
storage type, and adding our own compression scheme for coordinates.
* An uncompressed header, so header info can always be efficiently
"sliced" and read, even for very large objects
* A hash key for use in fast and small equality comparisons (for use
in cached comparison code)
* A compression format optimized for doubles
* Other compression formats with other tradeoffs (?) like TWKB for
higher ratio with precision loss
* Implies indirection in coordinate access again: smaller, more
efficient must be balanced against direct access to coordinates
* Move up to "modern" C and use whatever cool features we like from that
* Modern GEOS version requirement?
* Some major GEOS surgery to allow memory management by palloc?
* Some major GEOS surgery to build coordinateSequence directly on top
of PostGIS pointlists?
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-devel
--
Brian M Hamlin
OSGeo California
blog.light42.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20180117/9506f12b/attachment.html>
More information about the postgis-devel
mailing list