Re: Large index operation crashes postgres

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-25 20:31:40
Message-ID: 39af1ed21003251331x7ebc540elb17e768df0683f0b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Eliot Gable 2010-03-25 21:10:46 Performing FETCH ALL from a SCROLL CURSOR failing to return results
Previous Message Scott Marlowe 2010-03-25 20:15:24 Re: Does anyone use in ram postgres database?