[postgis-tickets] r15115 - use ST_Union instead of ST_Collect to compute raster max extent constraint
Regina Obe
lr at pcorp.us
Sun Sep 18 20:20:20 PDT 2016
Author: robe
Date: 2016-09-18 20:20:20 -0700 (Sun, 18 Sep 2016)
New Revision: 15115
Modified:
branches/2.2/NEWS
branches/2.2/raster/rt_pg/rtpostgis.sql.in
Log:
use ST_Union instead of ST_Collect to compute raster max extent constraint
References #3501 for PostGIS 2.2.3
Modified: branches/2.2/NEWS
===================================================================
--- branches/2.2/NEWS 2016-09-18 23:41:24 UTC (rev 15114)
+++ branches/2.2/NEWS 2016-09-19 03:20:20 UTC (rev 15115)
@@ -26,6 +26,8 @@
perl @INC fix (Sebastiaan Couwenberg)
- #3627, Encoded polyline functions ignore precision parameter
(Christian Quest / Dan Baston)
+ - #3501 use ST_Union instead of ST_Collect to compute
+ raster max extent constraint
PostGIS 2.2.2
Modified: branches/2.2/raster/rt_pg/rtpostgis.sql.in
===================================================================
--- branches/2.2/raster/rt_pg/rtpostgis.sql.in 2016-09-18 23:41:24 UTC (rev 15114)
+++ branches/2.2/raster/rt_pg/rtpostgis.sql.in 2016-09-19 03:20:20 UTC (rev 15115)
@@ -7148,7 +7148,7 @@
cn := 'enforce_max_extent_' || $3;
- sql := 'SELECT st_ashexewkb(st_envelope(st_collect(st_envelope('
+ sql := 'SELECT st_ashexewkb(st_envelope(st_union(st_envelope('
|| quote_ident($3)
|| ')))) FROM '
|| fqtn;
More information about the postgis-tickets
mailing list