Changes between Version 131 and Version 132 of UsersWikiPostgreSQLPostGIS


Ignore:
Timestamp:
Mar 27, 2018, 1:00:36 PM (6 years ago)
Author:
komzpa
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • UsersWikiPostgreSQLPostGIS

    v131 v132  
    2525^*^ Means it currently does or doesn't but may change at release time.
    2626
    27 Note we have dropped support for PostgreSQL 8.3 in PostGIS 2.0.
    28 
    29 We have dropped support for PostgreSQL 8.4 in PostGIS 2.1.
    30 
    31 We have dropped support for PostgreSQL 9.0 in PostGIS 2.2.
    32 We have dropped support for PostgreSQL 9.1 in PostGIS 2.3.
    33 
    34 We do not encourage PostgreSQL 9.2 + PostGIS 1.5, however PostGIS 1.5.6+ has patches to work with 9.2.
    35 
    3627If you are compiling PostGIS 2.0+ with anything less than 9.1,
    3728you will not get CREATE EXTENSION support and will also not get KNN gist distance for geometry.
    3829
    39 
    40 As a general rule, the PostGIS Project Steering committee  tries to maintain support of PostGIS for at least
    41 two versions of PostgreSQL. We most often support more than 2 PostgreSQL versions, if requirements do not
    42 necessitate bumping up requirement without too much effort. We will rarely support more than 5 PostgreSQL
    43 versions on any release.
     30As a general rule, the PostGIS Project Steering committee  tries to maintain support of PostGIS for at least two versions of PostgreSQL.
     31We most often support more than 2 PostgreSQL versions, if requirements do not necessitate bumping up requirement without too much effort.
     32We will rarely support more than 5 PostgreSQL versions on any release.
    4433
    453464-bit Windows version support started in PostGIS 2.0.0 (both 9.0 and 9.1)
    … …  
    5140The 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. 
    5241
     42For 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).
    5343
    54 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.
     44GEOS 3.1 brought cascade union.
     45
     46GEOS 3.2 brought faster buffering and buffering enhancements, plus numerous enhancements with dealing with tolerance issues when unioning.
     47
     48GEOS 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.
    5549
    5650GEOS 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+.  3.4 also brought [http://postgis.net/docs/manual-2.1/ST_DelaunayTriangles.html ST_DelaunayTriangles] so you won't get that in 2.1 if you don't compile for 3.4+.
    5751
    58 GEOS 3.5 brought some enhancements needed new features in PostGIS 2.2 [http://postgis.net/docs/manual-2.2/ST_Subdivide.html ST_Subdivide] and [http://postgis.net/docs/manual-2.2/ST_ClipByBox2D.html ST_ClipByBox2D]
    59 
     52GEOS 3.5 brought some enhancements needed new features in PostGIS 2.2 [http://postgis.net/docs/manual-2.2/ST_Subdivide.html ST_Subdivide] and [http://postgis.net/docs/manual-2.2/ST_ClipByBox2D.html ST_ClipByBox2D].
    6053GEOS 3.5 also brought ST_Voronoi so if compiled with lower than 3.5, the ST_Voronoi introduced in PostGIS 2.3 won't be available [http://postgis.net/docs/manual-2.3/ST_VoronoiLines.html ST_VoronoiLines and ST_VoronoiPolygons].
    6154
    62 GEOS 3.6.0 came out after 2.3.0 release, so most 2.3 distros will not have enabled - [http://postgis.net/docs/manual-2.3/ST_MinimumClearance.html ST_MinimumClearance*]  that require 3.6, but may in 2.3.1
     55GEOS 3.6.0 came out after 2.3.0 release, so most 2.3 distros will not have enabled - [http://postgis.net/docs/manual-2.3/ST_MinimumClearance.html ST_MinimumClearance*] that require 3.6, but may in 2.3.1
    6356
    6457||'''Geos Version'''||'''PostGIS 1.3 EOL'''||'''PostGIS 1.4 EOL'''||'''PostGIS 1.5 EOL'''||'''PostGIS 2.0 EOL'''||'''PostGIS 2.1 EOL'''||'''PostGIS 2.2'''||'''PostGIS 2.3'''||'''PostGIS 2.4'''
    … …  
    7568
    7669'''Versions of GDAL support for PostGIS'''
    77 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
    78 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.  * Means it currently does or doesn't but may change at release time.
     70
     71PostGIS raster functionality (introduced in 2.0) depends on GDAL so to get raster functionality, you'll need to compile with GDAL support and preferably 1.9 or above.
     72Although 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 :)).
     73For PostgreSQL 9.1 extension support, compiling with raster support is ABSOLUTELY required since the postgis extension includes the raster functionality.
     74
     75* Means it currently does or doesn't but may change at release time.
    7976
    8077