Vacuum full: alternatives?

Поиск
Список
Период
Сортировка
От Job
Тема Vacuum full: alternatives?
Дата
Msg-id 88EF58F000EC4B4684700C2AA3A73D7A07682A61343E@W2008DC01.ColliniConsulting.lan
обсуждение исходный текст
Ответы Re: Vacuum full: alternatives?  (Rakesh Kumar <rakeshkumar464a3@gmail.com>)
Re: Vacuum full: alternatives?  (Andreas Kretschmer <andreas@a-kretschmer.de>)
Re: Vacuum full: alternatives?  (Chris Ernst <cernst@zvelo.com>)
Re: Vacuum full: alternatives?  (Scott Marlowe <scott.marlowe@gmail.com>)
Список pgsql-general
Hello,

we have a table with an heavy traffic of pg_bulkload and delete of records.
The size pass, in only one day, for example for 1Gb to 4Gb and then 1Gb back.

We have important problems on size and the only way to gain free space is issueing a vacuum full <table>.
But the operation is very slow, sometimes 2/4 hours, and table is not available for services as it is locked.

We do not delete everything at one (in this case the truncate woudl resolve the problem).

The autovacuum is not able (same for normal vacuum) to free the spaces.

Are there some suggestions or another way to manage this?

Thank you!
Francesco

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

Предыдущее
От: Tatsuro Yamada
Дата:
Сообщение: Re: Pg_bulkload for PostgreSql 9.5
Следующее
От: Rakesh Kumar
Дата:
Сообщение: Re: Vacuum full: alternatives?