Skip site navigation (1) Skip section navigation (2)

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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Wayne Conrad <wconrad(at)yagni(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4730: Vacuum full verbose analyze "deadlock"
Date: 2009-03-25 19:19:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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                      
The PostgreSQL Company - Command Prompt, Inc.

In response to

pgsql-bugs by date

Next:From: cerieljacobsDate: 2009-03-25 19:56:10
Subject: BUG #4734: warning: oosp/uuid.h: present but cannot be compiled
Previous:From: Wayne ConradDate: 2009-03-25 18:05:08
Subject: Re: BUG #4730: Vacuum full verbose analyze "deadlock"

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group