Re: How overcome wait for vacuum full?

From: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: How overcome wait for vacuum full?
Date: 2007-05-16 01:28:08
Message-ID: 20070516012808.GF11533@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Purusothaman A 2007-05-16 05:42:01 OIDs - file objects, are damaged by PostgreSQL.
Previous Message Nick Urbanik 2007-05-16 01:20:52 Re: How overcome wait for vacuum full?