The 2.1.0rc1 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. 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.0rc1”;
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.0rc1”) , you need to first copy the file in share\extensions\postgis—2.0.3—2.1.0rc1.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.0dev and PostgreSQL 9.3beta2.
This release contains bug fixes completed since 2.1.0beta3 release:
View all closed tickets.
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 2.3.8 and 2.4.6 for the 2.3 and 2.4 stable branches.
The PostGIS development team is pleased to provide bug fix 2.2.8 for the 2.2 stable branch.
This is the End-Of-Life and final release for PostGIS 2.2 series.
We encourage you to upgrade to a newer minor PostGIS version. Refer to our Version compatibility and EOL Policy for details on versions you can upgrade to.
This release supports PostgreSQL 9.1-9.6.