[postgis-devel] PostGIS 3 thought experiment
dustymugs at gmail.com
Wed Jan 17 09:52:08 PST 2018
I'd love to do the following:
* create a new serialization for raster.
* default to uncompressed TOAST so that we can have uncompressed headers,
plug in different compression algorithms and tailor compression for each
* modern C would be fantastic
* within-object parallel processing. this is less significant for
geometry/geography but more for raster where i want to parallel process the
pixels of a tile. it may have value for pointcloud patches too
On Wed, Jan 17, 2018 at 9:44 AM, Paul Ramsey <pramsey at cleverelephant.ca>
> 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
> * 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the postgis-devel