Re: [HACKERS] Question regarding effects of Vacuum, Vacuum

Поиск
Список
Период
Сортировка
От Rod Taylor
Тема Re: [HACKERS] Question regarding effects of Vacuum, Vacuum
Дата
Msg-id 1037713599.83738.34.camel@jester
обсуждение исходный текст
Список pgsql-performance
Moving thread to pgsql-performance.

On Mon, 2002-11-18 at 22:02, Adrian Calvin wrote:
> Q - If many (eg hundreds) records are deleted (purposely), those
> records get flagged for later removal.  What is the best sequence of
> operations to optimize the database afterwards?  Is it Vacuum,
> Re-index, then do a Vacuum Analyze.

Just run a regular vacuum once for the above.  If you modify 10%+ of the
table (via single or multiple updates, deletes or inserts) then a vacuum
analyze will be useful.

Re-index when you change the tables contents a few times over. (Have
deleted or updated 30k entries in a table with 10k entries at any given
time).


General maintenance for a dataset of that size will probably simply be a
nightly vacuum, weekly vacuum analyze, and annual reindex or dump /
restore (upgrades).

--
Rod Taylor <rbt@rbt.ca>


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

Предыдущее
От: Federico /* juri */ Pedemonte
Дата:
Сообщение: Re: for/loop performance in plpgsql ?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: for/loop performance in plpgsql ?