Re: Need suggestion on how best to update 3 million rows - Mailing list pgsql-general

From Lincoln Yeoh
Subject Re: Need suggestion on how best to update 3 million rows
Date
Msg-id 200709061309.l86D9Y6H069952@smtp2.jaring.my
Whole thread Raw
In response to Re: Need suggestion on how best to update 3 million rows  (Richard Huxton <dev@archonet.com>)
Responses Re: Need suggestion on how best to update 3 million rows
List pgsql-general
At 06:32 PM 9/6/2007, Richard Huxton wrote:

>Two other tips for bulk-updates like this:
>1. Do as many columns in one go as you can
>2. Only update rows that need updating
>
>When you've finished, a CLUSTER/VACUUM FULL can be useful too.

How about: make sure you have enough free space because the table
will effectively double in size? Assuming it hasn't already been
updated a few times without vacuuming :).

That's still true right?

It is safe to assume that postgresql will still handle the out of
disk space scenario gracefully - no data corruption - the transaction
fails and that's it?

Regards,
Link.


pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Controlling locale and impact on LIKE statements
Next
From: "gunce orman"
Date:
Subject: foreign key violation error with partitioned table