Re: Large index operation crashes postgres

Operation is now running for around 13 hrs.
Two postmaster processes above 1% memory usage are running.

One of them uses constantly 26.5% of memory.
The other one is growing:
After 1 hr 25%
After 9 hrs 59%
After 13 hrs 64%

Thanks & regards
Frans

2010/3/25 Frans Hals <fhals7(at)googlemail(dot)com>:
> Paul,
>
> I have started the operation right now after a fresh reboot of the machine.
> <update placex set leakcheck = st_x(st_centroid(geometry));>
>  Please give me some time to collect the results...
>
> Thanks & regards
> Frans
>
> 2010/3/25 Paul Ramsey <pramsey(at)cleverelephant(dot)ca>:
>> If you build an index, or try to update a column, using just the
>>
>> ST_X(ST_Centroid())
>>
>> without all the extra pl/pgsql wrapping, do you still see the memory
>> footprint grow substantially?
>>
>> P.
>