From: Jim C. Nasby <jnasby@pervasive.com>
To: jody brownell <jody.brownell@q1labs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Help tuning autovacuum - seeing lots of relation bloat
Date: Wed, 21 Jun 2006 13:57:53 -0500
Message-ID: <20060621185752.GD93655@pervasive.com> (raw)
In-Reply-To: <200606211052.43227.jody.brownell@q1labs.com>
References: <200606211052.43227.jody.brownell@q1labs.com>
On Wed, Jun 21, 2006 at 10:52:42AM -0300, jody brownell wrote:
> A db wide vacuum full outputs this at the end.
>
> INFO: free space map contains 32848 pages in 159 relations
> DETAIL: A total of 24192 page slots are in use (including overhead).
> 24192 page slots are required to track all free space.
> Current limits are: 4024000 page slots, 2000 relations, using 23705 KB.
FWIW, the tail end of a db-wide vacuum FULL doesn't provide useful info
about FSM utilization, because it just made everything as compact as
possible.
My suspicion is that it's taking too long for autovac to get around to
this database/table. Dropping the sleep time might help. I see that this
table is vacuumed with a delay setting of 0, but if there are other
tables with a high delay that could pose a problem.
Getting detailed output of what autovac is actually doing as Tom
suggested would be a good idea.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jnasby@pervasive.com, jody.brownell@q1labs.com
Subject: Re: Help tuning autovacuum - seeing lots of relation bloat
In-Reply-To: <20060621185752.GD93655@pervasive.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox