Re: Running update in chunks? - Mailing list pgsql-general

From Jeff Janes
Subject Re: Running update in chunks?
Date
Msg-id CAMkU=1zEfWqz+Wj=FJPjXVuoiupLmZ7Rsd9PHwr1GiGQX1YMFg@mail.gmail.com
Whole thread Raw
In response to Re: Running update in chunks?  (Tim Uckun <timuckun@gmail.com>)
Responses Re: Running update in chunks?
Re: Running update in chunks?
List pgsql-general
On Monday, January 21, 2013, Tim Uckun wrote:
> First off, what does it say for rows affected? (Hint, if you really
> are using a default configuration and it doesn't say 0 rows
> affected, please show us the actual query used.)

update imports set make_id = null

Query returned successfully: 98834 rows affected, 49673 ms execution time.


vacuum analyze imports

Query returned successfully with no result in 4138 ms.

VACUUM FULL imports;

What if you do:
alter table cars.imports set (fillfactor=50);
Before the vacuum full, and then try the update again?
 
Cheers,

Jeff

pgsql-general by date:

Previous
From: Gavan Schneider
Date:
Subject: Re: Yet Another Timestamp Question: Time Defaults
Next
From: Jeff Janes
Date:
Subject: Re: Running update in chunks?