Changes between Version 60 and Version 61 of UsersWikiPostgreSQLPostGIS

Timestamp:

09/06/12 04:55:49 (12 years ago)

Author:

robe

Comment:

—

UsersWikiPostgreSQLPostGIS

@@ -33 +33 @@
 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 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://www.postgis.org/documentation/manual-svn/ST_DelaunayTriangles.html ST_DelaunayTriangles] so you won't get that in 2.1 if you don't compile for 3.4+.
 
 ||'''Geos Version'''||'''PostGIS 1.3'''||'''PostGIS 1.4'''||'''PostGIS 1.5'''||'''PostGIS 2.0'''||'''PostGIS 2.1 Trunk'''