Re: Running update in chunks?
| От | Jeff Janes |
|---|---|
| Тема | Re: Running update in chunks? |
| Дата | |
| Msg-id | CAMkU=1zEfWqz+Wj=FJPjXVuoiupLmZ7Rsd9PHwr1GiGQX1YMFg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Running update in chunks? (Tim Uckun <timuckun@gmail.com>) |
| Ответы |
Re: Running update in chunks?
Re: Running update in chunks? |
| Список | 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 по дате отправления: