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

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

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Wayne Conrad" <wconrad(at)yagni(dot)com>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #4730: Vacuum full verbose analyze "deadlock"
Date: 2009-03-25 21:00:30
Message-ID: 49CA551E.EE98.0025.0@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-bugs
Wayne Conrad <wconrad(at)yagni(dot)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

In response to

pgsql-bugs by date

Next:From: PalaffreDate: 2009-03-26 13:33:40
Subject: BUG #4736: Mediawiki by Postgres
Previous:From: cerieljacobsDate: 2009-03-25 19:56:10
Subject: BUG #4734: warning: oosp/uuid.h: present but cannot be compiled

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