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.
This is it, PostGIS 2.2 is almost out the door, so we’re looking for testing and feedback! Please give the release candidate a try and report back any issues you encounter.
View all closed tickets for 2.2.0.
Due to a number of bugs capable of crashing a back-end, we have released 2.1.8. If you are running an earlier version on a public site, we recommend that you update as soon as possible.
View all closed tickets for 2.1.8.
Due to a critical bug in GeoJSON ingestion we have made an early release of versions 2.0.7 and 2.1.7. If you are running an earlier version on a public site and accepting incoming GeoJSON, we recommend that you update as soon as possible.
View all closed tickets for 2.0.7.