Re: Best approach for large table maintenance

Поиск
Список
Период
Сортировка
От Decibel!
Тема Re: Best approach for large table maintenance
Дата
Msg-id EA01617F-D258-48B4-8E38-0625AF3D8AD2@decibel.org
обсуждение исходный текст
Ответ на Best approach for large table maintenance  ("Vanole, Mike" <MV5492@att.com>)
Список pgsql-general
Дерево обсуждения 
On Apr 22, 2008, at 12:04 PM, Vanole, Mike wrote:
> It seems that running vacuum still has value in the above approach
> because I still see index row versions were removed.


That means either part of the import failed (transaction aborted), or
you're updating or deleting rows between the load and the vacuum.
--
Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
Вложения

В списке pgsql-general по дате отправления:

Предыдущее
От: Ивайло Гелов
Дата:
Сообщение: Re: Strange behaviour - performance decreases after each TRUNCATE
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Alias in the HAVING clause