The PostGIS development team is pleased to provide bug fix 2.5.2, 2.4.7, and 2.3.9 for the 2.5, 2.4, and 2.3 stable branches.
These are the first versions to be able to compile against Proj 6.0.0, You must upgrade to these if you are using Proj 6.
2.5.2 This release supports PostgreSQL 9.3-11 (will compile against PostgreSQL 12, but not pass tests. Use only for pg_upgrade. You are encouraged to use the PostGIS 3.0 unreleased branch with PostgreSQL 12 , which has features specifically designed to take advantage of features new in PostgreSQL 12).
2.4.7 This release supports PostgreSQL 9.3-10.
This release supports PostgreSQL 9.2-10.
View all closed tickets for 2.5.2, 2.4.7, 2.3.9.
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 is pleased to provide bug fix and performance enhancements 3.0.2, 2.5.5, 2.4.9 for the 3.0, 2.5, and 2.4 stable branches.
The PostGIS Team is pleased to release the second alpha of upcoming PostGIS 3.1.0 release.
Best served with
PostgreSQL 13beta2, GEOS 3.7 or higher is recommended.
ST_MaximumInscribedCircle requires compilation with GEOS 3.9.0 in development to be enabled.
pgRouting 3.1.0 which will also be released soon.
The PostGIS Team is pleased to release PostGIS 2.3.11. This is the last bug fix release of the PostGIS 2.3 series. Please upgrade to 2.4 or higher if you want to continue receiving bug fixes.
If you come across any issues, feel free to report via our ticket tracker https://trac.osgeo.org/postgis or mailing list with details as described here. For security issues, send reports to firstname.lastname@example.org.