[postgis-devel] [PostGIS] #182: query leads to memory exhaustion

PostGIS trac at osgeo.org
Wed Sep 23 13:41:15 PDT 2009


#182: query leads to memory exhaustion
----------------------+-----------------------------------------------------
  Reporter:  akrherz  |       Owner:  pramsey
      Type:  defect   |      Status:  closed 
  Priority:  high     |   Milestone:         
 Component:  postgis  |     Version:         
Resolution:  wontfix  |    Keywords:         
----------------------+-----------------------------------------------------
Comment (by akrherz):

 Hi,

 Unfortunately, I am back with a reproducer again, with postgresql 8.4.1

 POSTGIS="1.4.0" GEOS="3.1.1-CAPI-1.6.0" PROJ="Rel. 4.6.1, 21 August 2008"
 USE_STATS

  select askml(setsrid(a,4326)) as kml, length(transform(a,2163)) as sz
        from (
  select
     intersection(
        buffer(exteriorring(geometryn(multi(geomunion(n.geom)),1)),0.02),
 exteriorring(geometryn(multi(geomunion(GeomFromEWKT('SRID=4326;MULTIPOLYGON(((-66.22
 18.38,-66.26 18.42,-66.25 18.47,-65.93 18.37,-65.97 18.29
 ,-66.22 18.38)))') )),1))
     ) as a
     from nws_ugc n WHERE
     ST_OverLaps(n.geom, GeomFromEWKT('SRID=4326;MULTIPOLYGON(((-66.22
 18.38,-66.26 18.42,-66.25 18.47,-65.93 18.37,-65.97 18.29,-66.22
 18.38)))') )
     and n.ugc IN ('PRC139', 'PRC031', 'PRC061', 'PRC021',
 'PRC137','PRC127')
  ) as foo
        WHERE not isempty(a)

 Does that query blow up for you too?  TIA!

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/182#comment:6>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS


More information about the postgis-devel mailing list