The 2.1.0rc2 release of PostGIS is now available.
The PostGIS development team is proud to release a release candidate version of upcoming PostGIS 2.1.0. As befits a minor release, the focus is on speed improvements, more features, and bug fixes. We expect this to be the final release candidate before we officially release 2.1.0 slated for Aug 12th, 2013. We’d appreciate it if you test it before final release and report back with any issues you run into so we can have a smooth release.
If you are currently using PostGIS 2.0 (or 2.1.0 beta3+) using extension support, you can go the soft upgrade path:
ALTER EXTENSION postgis UPDATE TO "2.1.0rc2";
If you are running 2.1.0 of beta or an unreleased version (and the above step fails with error “extension postgis has no update path from version x.x.x to version 2.1.0rc2”) , you need to first copy the file in share\extensions\postgis—2.0.3—2.1.0rc2.sql and change the 2.0.3 to the x.x.x noted in the error you are running. Then follow the above upgrade step again.
Users of 1.5 and below will need to go the hard-upgrade path.
Best served with a bottle of GEOS 3.4.0 (planned release Aug 11th) and PostgreSQL 9.3beta2.
This release contains bug fixes completed since 2.1.0rc1 release:
View all closed tickets.
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.
The PostGIS Team is pleased to release PostGIS 2.5.4.
The PostGIS Team is pleased to release PostGIS 3.0.1.
Best served with PostgreSQL 12.2, GEOS 3.8.0, SFCGAL 1.3.7, GDAL 3.0.4, PROJ 6.3.1, protobuf-c 1.3.3, json-c 0.13.1.