Re: BUG #4730: Vacuum full verbose analyze "deadlock" - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: BUG #4730: Vacuum full verbose analyze "deadlock"
Date
Msg-id 49CA551E.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Re: BUG #4730: Vacuum full verbose analyze "deadlock"  (Wayne Conrad <wconrad@yagni.com>)
List 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 by date:

Previous
From: "Thompson, Eric"
Date:
Subject: Re: BUG #4721: All sub-tables incorrectly included in search plan for partitioned table
Next
From: "Palaffre"
Date:
Subject: BUG #4736: Mediawiki by Postgres