[geos-devel] Fwd: [GENERAL] Large index operation crashes postgres
Can anyone valgrind the capi centroid call on a 2-point linestring and see if it leaks? It seems like it might... P -- Forwarded message -- From: Frans Hals fha...@googlemail.com Date: Mon, Mar 29, 2010 at 10:17 AM Subject: Re: [GENERAL] Large index operation crashes postgres To: Paul Ramsey pram...@cleverelephant.ca Cc: pgsql-gene...@postgresql.org Paul, I have checked the different kinds of data in the table for their memory usage. ST_LineSting is the one that's leaking, the other types complete indexing without leakage. Update to Geos 3.2.0 didn't improve the operation. Kind regards Frans 2010/3/28 Paul Ramsey pram...@cleverelephant.ca: MIght be random, might be a clue, we'll see. So it looks like much of the table is two-point lines and points. P On Sat, Mar 27, 2010 at 1:16 PM, Frans Hals fha...@googlemail.com wrote: ST_Point | | 20648939 ST_MultiPolygon | | 6188 ST_Polygon | | 8054680 ___ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel
Re: [geos-devel] Fwd: [GENERAL] Large index operation crashes postgres
On Mon, Mar 29, 2010 at 10:29:06AM -0700, Paul Ramsey wrote: Can anyone valgrind the capi centroid call on a 2-point linestring and see if it leaks? It seems like it might... Tried this: LINESTRING(0 0, 10 0) No leaks in C-API from 3.2 branch What's the one exposing the bug ? --strk; () Free GIS Flash consultant/developer /\ http://strk.keybit.net/services.html ___ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel
Re: [geos-devel] Fwd: [GENERAL] Large index operation crashes postgres
Well, my best bet was that it as the call to centroid. Apparently it manifests in 3.1 and 3.2 branches, but perhaps it's somewhere else. (Not sure where.) P On Mon, Mar 29, 2010 at 12:19 PM, strk s...@keybit.net wrote: On Mon, Mar 29, 2010 at 10:29:06AM -0700, Paul Ramsey wrote: Can anyone valgrind the capi centroid call on a 2-point linestring and see if it leaks? It seems like it might... Tried this: LINESTRING(0 0, 10 0) No leaks in C-API from 3.2 branch What's the one exposing the bug ? --strk; () Free GIS Flash consultant/developer /\ http://strk.keybit.net/services.html ___ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel ___ geos-devel mailing list geos-devel@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/geos-devel
