Re: BUG #4730: Vacuum full verbose analyze "deadlock"

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: BUG #4730: Vacuum full verbose analyze "deadlock"
Дата
Msg-id 49CA551E.EE98.0025.0@wicourts.gov
обсуждение исходный текст
Ответ на Re: BUG #4730: Vacuum full verbose analyze "deadlock"  (Wayne Conrad <wconrad@yagni.com>)
Список pgsql-bugs
Wayne Conrad <wconrad@yagni.com> wrote:
> the database started getting slow over time.

As Alvaro pointed out, this can happen if your fsm configuration
doesn't allow enough space for a normal VACUUM to keep track of all
the free space.  Since you're running VACUUM with the VERBOSE option,
be sure to capture the output and review the last few lines; this will
tell you what setting you have and the minimum which would cover
current needs.

Also, be sure you haven't disabled autovacuum along the way.

There are some usage patterns which require special forms of
maintenance, but VACUUM FULL usually isn't the best option for routine
maintenance.  If you notice performance degrading again, please post
details on the performance list.

I hope this helps.

-Kevin

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

Предыдущее
От: "Thompson, Eric"
Дата:
Сообщение: Re: BUG #4721: All sub-tables incorrectly included in search plan for partitioned table
Следующее
От: "Palaffre"
Дата:
Сообщение: BUG #4736: Mediawiki by Postgres