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 2.1.4 release of PostGIS is now available.
The PostGIS development team is happy to release patch for PostGIS 2.1, the 2.1.4 release. As befits a patch release, the focus is on bugs, breakages, and performance issues
It has come to our attention that the PostGIS Raster support may give more privileges to users than an administrator is willing to grant. These include reading files from the filesystem and opening connections to network hosts.
The 2.0.5 release of PostGIS is now available.
The PostGIS development team is happy to release patch for PostGIS 2.0, the 2.0.5 release. As befits a patch release, the focus is on bugs and breakages.
Best served with a bottle of GEOS 3.3.9.