| | 1 | == Purpose |
| | 2 | |
| | 3 | This page is not a list of things that **will happen** it is a place to gather disruptive changes that might make sense for a PostGIS 3 release. |
| | 4 | |
| | 5 | == Ideas |
| | 6 | |
| | 7 | * Break out a `postgis_raster` extension with a `postgis` dependency, so raster support becomes optional. |
| | 8 | * Require installation in a 'postgis' schema, always and for ever |
| | 9 | * Yet another serialization, this time changing to use `external` storage type, and adding our own compression scheme for coordinates. |
| | 10 | * An uncompressed header, so header info can always be efficiently "sliced" and read, even for very large objects |
| | 11 | * A hash key for use in fast and small equality comparisons (for use in cached comparison code) |
| | 12 | * A compression format optimized for doubles |
| | 13 | * Other compression formats with other tradeoffs (?) like TWKB for higher ratio with precision loss |
| | 14 | * Implies indirection in coordinate access again: smaller, more efficient must be balanced against direct access to coordinates |
| | 15 | * Move up to "modern" C and use whatever cool features we like from that |
| | 16 | * Modern GEOS version requirement? |
| | 17 | * Some major GEOS surgery to allow memory management by palloc? |
| | 18 | * Some major GEOS surgery to build CoordinateSequence directly on top of PostGIS pointlists? |
