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

From Alvaro Herrera
Subject Re: BUG #4730: Vacuum full verbose analyze "deadlock"
Date
Msg-id 20090325191900.GQ16373@alvh.no-ip.org
Whole thread Raw
In response to Re: BUG #4730: Vacuum full verbose analyze "deadlock"  (Wayne Conrad <wconrad@yagni.com>)
List pgsql-bugs
Wayne Conrad wrote:

> We started doing a routine VACUUM FULL ANALYZE on the advice of a
> friend after the database started getting slow over time.  We did not
> realize that the FULL should never be done.  We will change that to a
> VACUUM ANALYZE, without the full, and see how it goes.
>
> We discovered that an occasionally REINDEX was also required to keep
> things fast.  We did not realize it was a direct result of the VACUUM
> FULL that the REINDEX was required.

You probably need to increase the size of the free space map too.  See
the fsm_max_pages parameter in postgresql.conf.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-bugs by date:

Previous
From: Wayne Conrad
Date:
Subject: Re: BUG #4730: Vacuum full verbose analyze "deadlock"
Next
From: ""
Date:
Subject: BUG #4734: warning: oosp/uuid.h: present but cannot be compiled