From: | Nick Urbanik <nicku(at)nicku(dot)org> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: How overcome wait for vacuum full? |
Date: | 2007-05-16 01:20:52 |
Message-ID: | 20070516012052.GC16310@nicku.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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.
--
Nick Urbanik RHCE http://nicku.org nicku(at)nicku(dot)org
GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2007-05-16 01:28:08 | Re: How overcome wait for vacuum full? |
Previous Message | Nick Urbanik | 2007-05-16 01:18:04 | Re: How far does interrupting vacuum full rollback? |