The PostGIS development team is pleased to announce the release of PostGIS 2.4.0beta1. PostGIS 2.4.0 will be the first version to support PostgreSQL 10. Best served with PostgreSQL 10beta4 and pgRouting 2.5.0beta See the full list of changes in the news file.
We encourage everyone to test and in particular package maintainers to insure no surprises at final release time.
From this point forward until release of PostGIS 2.4.0, no new functions will be added.
Only bug fixes will be addressed in future 2.4.0 betas and rcs.
In order to have Map Box Vector Tiles support enabled, you’ll need to compile with protobuf support and pkg-config to verify the correct minimum version of protobuf-c see protobuf for details. ST_FrechetDistance function will not be enabled if PostGIS is compiled with lower than GEOS 3.7.0. GEOS 3.7.0 will be released around the same time as PostGIS 2.4.0 and will have a beta release in a week.
Please report bugs that you find in this release.
View all closed tickets for 2.4.0.
The PostGIS development team is pleased to provide bug fix release 2.3.6 and 2.4.3 for the 2.3 and 2.4 stable branches.
Key fixes in these releases are Brin upgrade, ST_Transform schema qualification to fix issues with restore, foreign table, and materialized view use, ClusterKMeans and encoded polyline fixes.
View all closed tickets for 2.4.3 and 2.3.6.
After installing the binaries or after running pg_upgrade, make sure to do:
ALTER EXTENSION postgis UPDATE;
— if you use the other extensions packaged with postgis — make sure to upgrade those as well
ALTER EXTENSION postgis_sfcgal UPDATE; ALTER EXTENSION postgis_topology UPDATE; ALTER EXTENSION postgis_tiger_geocoder UPDATE;
If you use legacy.sql or legacy_minimal.sql, make sure to rerun the version packaged with these releases.
The PostGIS development team has uploaded bug fix releases for the 2.3 and 2.4 stable branches.
The PostGIS development team has uploaded bug fix releases for the 2.2, 2.3 and 2.4 stable branches.