| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Nick Urbanik <nicku(at)nicku(dot)org> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: How overcome wait for vacuum full? |
| Date: | 2007-05-16 01:12:52 |
| Message-ID: | 20070516011252.GW12731@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Nick Urbanik wrote:
> Thank you Alvaro,
>
> 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.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nick Urbanik | 2007-05-16 01:18:04 | Re: How far does interrupting vacuum full rollback? |
| Previous Message | Jim C. Nasby | 2007-05-16 00:59:54 | Re: How far does interrupting vacuum full rollback? |