Re: Large index operation crashes postgres - Mailing list pgsql-general

From Frans Hals
Subject Re: Large index operation crashes postgres
Date
Msg-id 39af1ed21003291017k46b0480en2fe37b27f22bc5fb@mail.gmail.com
Whole thread Raw
In response to Large index operation crashes postgres  (Frans Hals <fhals7@googlemail.com>)
List 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@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@googlemail.com> wrote:
>
>>  ST_Point        |              | 20648939
>>  ST_MultiPolygon |              |     6188
>>  ST_Polygon      |              |  8054680

pgsql-general by date:

Previous
From: Bill Moran
Date:
Subject: Re: How long will the query take
Next
From: Harald Fuchs
Date:
Subject: Re: How to perform text merge