Re: Running update in chunks?
Jeff Janes <jeff.janes@gmail.com>
From: Jeff Janes <jeff.janes@gmail.com>
To: Tim Uckun <timuckun@gmail.com>
Cc: Kevin Grittner <kgrittn@mail.com>, Richard Huxton <dev@archonet.com>, "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Date: 2013-01-22T07:02:57Z
Lists: 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