|Version 58 (modified by 10 years ago) ( diff ),|
Versions of PostgreSQL supported by which versions of PostGIS
|PostgreSQL Version||PostGIS 1.3||PostGIS 1.4||PostGIS 1.5||PostGIS 2.0||PostGIS 2.1 Trunk|
|7.2-7.4||Yes (not windows)||No||No||No||No|
|8.0||Yes (not windows)||No||No||No||No|
Note we have dropped support for PostgreSQL 8.3 in PostGIS 2.0. We are planning to drop support for PostgreSQL 8.4 in PostGIS 2.1. PostgreSQL 9.1 has now been released. PostgreSQL 9.2 (still in development) though it can currently compile against 2.0, we don't guarantee it will at release time. ,9.2 will definitely work with 2.1 at release time. That we guarantee.
As a general rule, the PostGIS Project Steering committee tries to maintain support of PostGIS for at least two versions of PostgreSQL. We most often support more than 2 PostgreSQL versions, if requirements do not necessitate bumping up requirement without too much effort. We will rarely support more than 4 PostgreSQL versions on any release.
64-bit Windows version support started in PostGIS 2.0.0 (both 9.0 and 9.1)
Versions of GEOS support for PostGIS
The below chart shows which versions of GEOS work with which versions of PostGIS. The none means that you can get that version to work without GEOS, though its not recommended since a lot of functions will not be installed.
For the not recommended, this means that while you can get PostGIS to work with those versions, you'll be missing out on some PostGIS functions such as ST_Covers, ST_CoversBy and for PostGIS 1.5 the ST_HausdorffDistance and enhancements to ST_Buffer (both speed and functionality). GEOS 3.1 brought cascade union. GEOS 3.2 brought faster buffering and buffering enhancements, plus numerous enhancements with dealing with tolerance issues when unioning. GEOS 3.3 brought ST_ValidReason, ST_MakeValid etc (in the PostGIS 2.0 releases), so these functions will be disabled in PostGIS 2.0 if you are not running GEOS 3.3. GEOS 3.3. also brought stability fixes for union/buffer not back-ported to 3.2. For PostGIS 1.5, although 3.3 does not add any additional functions, it does fix some crashers involving buffering and unioning not present in other minor releases, so suggested to use that if you can.
GEOS 3.4 introduced interruptibility features that allow you to cancel a query while in a GEOS loops. Prior versions of PostGIS/GEOS a query could run (even with statement timeout) until you ran out of memory. This new feature requires both PostGIS 2.1 and GEOS 3.4+
|Geos Version||PostGIS 1.3||PostGIS 1.4||PostGIS 1.5||PostGIS 2.0||PostGIS 2.1 Trunk|
|None||Yes (not recommended)||No||No||No||No|
|2.2||Yes (not recommended)||No||No||No||No|
|3.0||Yes||Yes (not recommended)||No||No||No|
|3.1||Yes||Yes||Yes (not recommended) (requires 3.1.1+)||No||No|
|3.2||Yes||Yes||Yes||Yes (not recommended)||No|
|3.3||Yes||Yes||Yes (preferred 3.3.3+)||Yes (3.3.3+)||Yes (not recommended)|
|3.4||Yes||Yes||Yes (preferred 3.3.3+)||Yes (3.3.3+)||Yes (preferred)|
Versions of GDAL support for PostGIS PostGIS raster functionality (introduced in 2.0) depends on GDAL so to get raster functionality, you'll need to compile with GDAL support and preferrably 1.9 or above. Although you can compile PostGIS 2.0 without raster support, you really should rethink that decision, especially if you are a package maintainer (you'll have a lot of pissed off users if you do ). For PostgreSQL 9.1 extension support, compiling with raster support is ABSOLUTELY required since the postgis extension includes the raster functionality.
|GDAL Version||Pre - PostGIS 2.0||PostGIS 2.0||PostGIS 2.1 Trunk|
|1.7||N/A||Yes (not recommended)||No|
|1.8||N/A||Yes (not recommended)||Yes (not recommended)|