Re: Long Running Update

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Harry Mantheakis" <harry(dot)mantheakis(at)riskcontrollimited(dot)com>
Cc: "Claudio Freire" <klaussfreire(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Long Running Update
Date: 2011-06-24 16:41:38
Message-ID: 4E0477F2020000250003EBCA@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Harry Mantheakis <harry(dot)mantheakis(at)riskcontrollimited(dot)com> wrote:

> I have stopped the all-in-one-go update from executing, and now I
> am executing a series of statements, each constrained to update no
> more than 100,000 records at a time.
>
> Interesting fact: updating 100,000 rows takes 5 seconds. Quick.

One last thing -- all these updates, included the aborted attempt at
a single-pass update, may cause significant bloat in both the heap
and the index(es). I usually finish up with a CLUSTER on the table,
followed by a VACUUM ANALYZE on the table.

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Harry Mantheakis 2011-06-24 16:49:55 Re: Long Running Update
Previous Message Harry Mantheakis 2011-06-24 16:31:38 Re: Long Running Update