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

From Frans Hals
Subject Re: Large index operation crashes postgres
Date
Msg-id 39af1ed21003251331x7ebc540elb17e768df0683f0b@mail.gmail.com
Whole thread Raw
In response to Large index operation crashes postgres  (Frans Hals <fhals7@googlemail.com>)
Responses Re: Large index operation crashes postgres  (Frans Hals <fhals7@googlemail.com>)
List pgsql-general
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@cleverelephant.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.

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: Does anyone use in ram postgres database?
Next
From: Eliot Gable
Date:
Subject: Performing FETCH ALL from a SCROLL CURSOR failing to return results