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 <pramsey@xxxxxxxxxxxxxxxxx>: > 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@xxxxxxxxxxxxxx> wrote: > >> ST_Point | | 20648939 >> ST_MultiPolygon | | 6188 >> ST_Polygon | | 8054680 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general