Re: Massive table (500M rows) update nightmare

> crank it up more and delay the checkpoints as much as possible during
> these updates.  64 segments is already 1024M.

We have 425M rows, total table size is 78GB, so we can imagine a worst case
UPDATE write is less than 200 bytes * number of rows specified in the update
(is that logic correct?).

Inerestingly, the total index size is 148GB, twice that of the table, which
may be an indication of where the performance bottleneck is.