[OSGeo-Discuss] PostGIS 2.5.0rc2 release
Regina Obe
lr at pcorp.us
Sun Sep 16 21:30:03 PDT 2018
The PostGIS development team is pleased to release PostGIS 2.5.0rc2.
Blog: http://postgis.net/2018/09/16/postgis-2.5.0rc2/
Although this release will work for PostgreSQL 9.4 and above, to take full
advantage of
what PostGIS 2.5 offers, you should be running PostgreSQL 11beta3+ and GEOS
3.7.0.
Source: https://download.osgeo.org/postgis/source/postgis-2.5.0rc2.tar.gz
Documentation PDF: English:
https://download.osgeo.org/postgis/docs/postgis-2.5.0rc2.pdf
German:
https://download.osgeo.org/postgis/docs/https://postgis.net/stuff/postgis-2.
5.0rc2-de.pdf
Html Documentation:
https://download.osgeo.org/postgis/docs/doc-html-2.5.0rc2.tar.gz
pgsql help files for non-english languages:
German:
https://download.osgeo.org/postgis/docs/pgsql-help-2.5-de.tar.gz ,
Japanese:
https://download.osgeo.org/postgis/docs/pgsql-help-2.5-ja.tar.gz
Korean:
https://download.osgeo.org/postgis/docs/pgsql-help-2.5-kr.tar.gz
Portuguese:
https://download.osgeo.org/postgis/docs/pgsql-help-2.5-br.tar.gz
Spanish:
https://download.osgeo.org/postgis/docs/pgsql-help-2.5-es.tar.gz
Change Log: https://svn.osgeo.org/postgis/tags/2.5.0rc2/ChangeLog
WARNING: If compiling with PostgreSQL 11++JIT, LLVM >= 6 is required
Changes since PostGIS 2.5.0rc1 release are as follows:
4162, ST_DWithin documentation examples for storing geometry and radius
in table (Darafei Praliaskouski, github user Boscop).
4163, MVT: Fix resource leak when the first geometry is NULL (Raúl
Marín)
4172, Fix memory leak in lwgeom_offsetcurve (Raúl Marín)
4164, Parse error on incorrectly nested GeoJSON input (Paul Ramsey)
4176, ST_Intersects supports GEOMETRYCOLLECTION (Darafei Praliaskouski)
4177, Postgres 12 disallows variable length arrays in C (Laurenz Albe)
4160, Use qualified names in topology extension install (Raúl Marín)
4180, installed liblwgeom includes sometimes getting used instead of
source ones (Regina Obe)
We hope this will be the last RC before final release. Please help us test.
Thanks,
PostGIS Development Team
More information about the Discuss
mailing list