From: Jim C. Nasby <decibel@decibel.org>
To: pgsql-admin@postgresql.org
Subject: Re: How overcome wait for vacuum full?
Date: Tue, 15 May 2007 20:28:08 -0500
Message-ID: <20070516012808.GF11533@nasby.net> (raw)
In-Reply-To: <20070516012052.GC16310@nicku.org>
References: <20070515221356.GG5264@nicku.org>
<20070515225313.GV12731@alvh.no-ip.org>
<20070515231616.GH5264@nicku.org>
<20070516011252.GW12731@alvh.no-ip.org>
<20070516012052.GC16310@nicku.org>
On Wed, May 16, 2007 at 11:20:52AM +1000, Nick Urbanik wrote:
> Dear Alvaro,
>
> On 15/05/07 21:12 -0400, Alvaro Herrera wrote:
> >Nick Urbanik wrote:
> >>On 15/05/07 18:53 -0400, Alvaro Herrera wrote:
> >>>Instead of waiting a month for the time when you can take the
> >>>application offline (thus accumulating a month's worth of dead tuples),
> >>>run a non-full vacuum more often (say, once a day or more). It doesn't
> >>>lock the table so the app can continue to be online while it runs.
> >>
> >>Yes, it is vacuumed non-full regularly. However, for some reason,
> >>only a full vacuum will recover the space.
> >
> >You probably need to better configure the FSM settings. See
> >fsm_max_pages in the docs.
>
> This is probably the critical piece of information we need to prevent
> the need for another sleepless night and an outage! Thank you.
http://www.pervasive-postgres.com/instantkb13/article.aspx?id=10087&cNode=5K1C3W
might be of use as well.
--
Jim Nasby decibel@decibel.org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
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-admin@postgresql.org
Cc: decibel@decibel.org
Subject: Re: How overcome wait for vacuum full?
In-Reply-To: <20070516012808.GF11533@nasby.net>
* 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