[postgis-devel] Postgis 3.1 minimum requirements update

Darafei "Komяpa" Praliaskouski me at komzpa.net
Mon Nov 11 07:16:25 PST 2019


>
>
> > Minimum PG version: 9.6 (was 9.5)
> ....
> What's the gain of changing this, to offset the pain caused by people
> using 9.5?
>

PostGIS 3.1 is going to be released around the time 9.5 will become End of
Life.


> Recommended GEOS version: 3.8 (was 3.7)
>
> 'Recommended" in a vacuum is odd, because the standard approach is to
> run the most recent release from a given project, eccept that after big
> changes it is sensible to hold off 3-6 months.  And, releases that
> withdraw APIs have a much longer time before they can be considered
> generally recommended (e.g. proj).
>

Setting GEOS 3.8 as minimum (instead of "recommended") will let us lose a
large amount of code that was shifted into it from liblwgeom, including but
not limited to MakeValid, and guarantee that all the users get all the
functionality including the Frechet distance.
It will also let us ship Coverage Union as a function without the "alas
your distro maintainer built postgis without it" curse.
We will still have some variablility because of upcoming GEOS 3.9/4.0, but
keeping it at manageable level is generally a good idea.

Previously I proposed to also bump GDAL to 2.1 and PROJ to 4.9 for PostGIS
3.0. This did not come through as it was rather late in previous cycle, but
getting it (or a year in the future stricter) would be good. This also lets
us remove some quirks.

https://github.com/Komzpa/postgis/tree/ticket-4455


-- 
Darafei Praliaskouski
Support me: http://patreon.com/komzpa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20191111/74c2c350/attachment.html>


More information about the postgis-devel mailing list