[geos-devel] Fwd: [GENERAL] Large index operation crashes postgres

Paul Ramsey pramsey at cleverelephant.ca
Mon Mar 29 13:29:06 EDT 2010

Can anyone valgrind the capi centroid call on a 2-point linestring and
see if it leaks? It seems like it might...

---------- Forwarded message ----------
From: Frans Hals <fhals7 at googlemail.com>
Date: Mon, Mar 29, 2010 at 10:17 AM
Subject: Re: [GENERAL] Large index operation crashes postgres
To: Paul Ramsey <pramsey at cleverelephant.ca>
Cc: pgsql-general at postgresql.org


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

2010/3/28 Paul Ramsey <pramsey at 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 <fhals7 at googlemail.com> wrote:
>>  ST_Point        |              | 20648939
>>  ST_MultiPolygon |              |     6188
>>  ST_Polygon      |              |  8054680

More information about the geos-devel mailing list