From: | Frans Hals <fhals7(at)googlemail(dot)com> |
---|---|
To: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Large index operation crashes postgres |
Date: | 2010-03-29 17:17:27 |
Message-ID: | 39af1ed21003291017k46b0480en2fe37b27f22bc5fb@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(at)cleverelephant(dot)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(dot)com> wrote:
>
>> ST_Point | | 20648939
>> ST_MultiPolygon | | 6188
>> ST_Polygon | | 8054680
From | Date | Subject | |
---|---|---|---|
Next Message | Harald Fuchs | 2010-03-29 17:35:38 | Re: How to perform text merge |
Previous Message | Bill Moran | 2010-03-29 17:10:59 | Re: How long will the query take |