[postgis-devel] [PostGIS] #577: possible memory leak with buffer()

[PostGIS]

#577: possible memory leak with buffer()
-----------------------+----------------------------------------------------
  Reporter:  davideps  |       Owner:  robe                           
      Type:  defect    |      Status:  closed                         
  Priority:  medium    |   Milestone:                                 
 Component:  postgis   |     Version:  1.3.X                          
Resolution:  invalid   |    Keywords:  memory buffer intersect dwithin
-----------------------+----------------------------------------------------
Changes (by robe):

  * status:  new => closed
  * resolution:  => invalid


Comment:

 David,

 Those particular questions should be asked on PostGIS users list since
 they are not bugs.

 For upgrading GEOS 3.1 is more or less fine when using 1.3.  I don't think
 you'll gain much.  In theory you can get away with just upgrading GEOS
 without PostGIS as long as your symlinks are appropriately set (since GEOS
 3.2 (superset) is a drop in replace for 3.1)

  As with most things, it depends.  It depends on the complexity of your
 geometries, the area of the polygons, how close they are together etc.  It
 could be anywhere from milliseconds to minutes depending on those factors
 and not knowing the details we can't give you an answer.

 I've run queries (as most people have) on much larger polygon sets and
 they finish in a fraction of a second (then again the number of records in
 those cases is probably about 100-1000 for results  or so and I chop up my
 polygons if they get too large or simplify them so they have fewer points
 when speed becomes an issue)

 You really need to do an EXPLAIN (faster but less detailed)  or an EXPLAIN
 ANALYZE (takes about same time as your query minus time to output, but
 gives more detail)  your query.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/577#comment:4>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.