[postgis-devel] PSC Vote: Next release after 2.5 minor series will be 3.0

[Paul Ramsey]

I think the wiki page outlines some of the desired changes. To an extent they can be made “backwards compatible” for older installations, using the version flags in gserialized. Things like an uncompressed header area, some kind of double-optimized compression on coordinate lists, perhaps an expandable header ala twkb, and use of ‘external’ storage to avoid the application of pglz compression to the (already compressed) coordinate lists.

The goal being faster access to header information for large objects. There’s a lot of potential balancing to do w/ that kind of format, including things like leaving smaller objects uncompressed for direct double access, etc, etc. It’s unfortunately a fair amount of work with unknown benefits, though to the extent the pglz consistently shows up as a major call point when profiling spatial joins, potentially quite worth it.

P

> On Jul 9, 2018, at 1:45 PM, Darafei Komяpa Praliaskouski <me at komzpa.net> wrote:
> 
> What changes in on disk format are needed? Can they be solved by making a new type of geometry that will hold new format internally, and keep readers/headers for current format? This way the migration can be seamless and delayed and done even in minor. 
> 
> On пн, 9 ліп 2018, 23:05 Paul Ramsey <pramsey at cleverelephant.ca <mailto:pramsey at cleverelephant.ca>> wrote:
> Well, that’s a big change and I was hoping to hold 3 for a change in the disk format rather than burn it for administrivia… interested to hear what others have to say. +/- 0
> P
> 
> > On Jul 9, 2018, at 1:03 PM, Regina Obe <lr at pcorp.us <mailto:lr at pcorp.us>> wrote:
> > 
> > We've been quietly toying with this idea, but would like to put in stone.
> > 
> > Instead of having yet another minor of 2, let's go to 3.0.
> > 
> > Hey we went from 1.5 to 2, seems appropriate to go from 2.5 to 3.
> > 
> > All PostGIS developers and packagers I'd like your feedback too since it
> > will sway our decision.
> > 
> > My main reason for wanting to jump to 3.0 is so we can standardize on
> > dropping the minor version in our  lib file.
> > 
> > So that means 3.0 would have a lib file
> > postgis-3.whatever_extension_os_prefers.
> > 
> > 
> > No postgis-3.0  etc.  just postgis-3
> > 
> > And thenceforth all PostGIS from 3.0 on will no longer have the .minor
> > version and we will promise as a project to ensure we will not remove C-API
> > functions referenced in prior 3.whatever  SQL api and never do so during the
> > series of a major release.
> > Thus making pg_upgrade possible without having install an older version of
> > PostGIS or to do hacks symlink  lib files from older versions to newer or
> > having people have to ask us - is it okay to symlink?
> > 
> > +1 for 3.0 
> > 
> > Here are some other things on table for 3.0
> > 
> > https://trac.osgeo.org/postgis/wiki/PostGIS3 <https://trac.osgeo.org/postgis/wiki/PostGIS3>  (breakout of postgis raster I
> > am totally against :) )
> > 
> > don't forget we've got a code sprint coming up this September to discuss
> > this and other topics.  Signup so we know how many people to expect.
> > 
> > https://trac.osgeo.org/postgis/wiki/PostGISCodeSprint2018 <https://trac.osgeo.org/postgis/wiki/PostGISCodeSprint2018>
> > 
> > 
> > If you are only going to join remotely, it's okay to put your name on their
> > but with note (Remote)
> > 
> > Thanks,
> > Regina
> > 
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org>
> > https://lists.osgeo.org/mailman/listinfo/postgis-devel <https://lists.osgeo.org/mailman/listinfo/postgis-devel>
> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org>
> https://lists.osgeo.org/mailman/listinfo/postgis-devel <https://lists.osgeo.org/mailman/listinfo/postgis-devel>_______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20180709/ac922090/attachment.html>