The 2.1.0 release of PostGIS is now available.
The PostGIS development team is proud to release PostGIS 2.1.0. As befits a minor release, the focus is on speed improvements, more features, and bug fixes.
If you are currently using PostGIS 2.0+, you can go the soft upgrade path:
ALTER EXTENSION postgis UPDATE TO "2.1.0";
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.0”) , you need to first copy the file in share\extensions\postgis—2.0.3—2.1.0.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 documented in manual:
Best served with a bottle of GEOS 3.4.1 and PostgreSQL 9.3beta2 (planned release September).
This release contains bug fixes completed since 2.1.0rc2 release:
This release contains a ton of speed improvements, function additions , and super sexy new features. It has been over a year in the making.
New functions itemized in http://postgis.net/docs/manual-2.1/PostGIS_Special_Functions_Index.html#NewFunctions_2_1
Important / Breaking Changes
View all closed tickets.
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.