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 Team is pleased to release the first alpha of the upcoming PostGIS 3.2.0 release.
Best served with PostgreSQL 14 beta3. This version of PostGIS utilizes the faster GiST building support API introduced in PostgreSQL 14. If compiled with the in-development GEOS 3.10dev you can take advantage of improvements in ST_MakeValid. This release also includes many additional functions and improvements for
The PostGIS development team is pleased to provide bug fix and performance enhancements 3.1.4 and 3.0.4 for the 3.1, 3.0 stable branches.
3.1.4 This release supports PostgreSQL 9.6-14.
3.0.4 This release works with PostgreSQL 9.5-13 and GEOS >= 3.6 Designed to take advantage of features in PostgreSQL 12+ and Proj 6+
View all closed tickets for 3.1.4, 3.0.4.
After installing the binaries or after running pg_upgrade:
For PostGIS 3.1, 3.0, 2.5 do below which will upgrade all your postgis extensions.
For PostGIS 2.4 and below 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 Team is pleased to release PostGIS 3.1.3! Best Served with PostgreSQL 14 beta2.
This release is a bug fix release, addressing issues found in the previous 3.1 release.
#4929, Fix missing error from GetRingEdges when invoked with unexistent topology or edge (Sandro Santilli)
#4927, Fix PostgreSQL 14 compile FuncnameGetCandidates changes needed to compile against PostgreSQL 14 beta2 or higher (Regina Obe, Julien Rouhaud)