| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Anibal David Acosta <aa(at)devshock(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: where is max_fsm_pages in PG9.0? |
| Date: | 2011-09-20 04:49:50 |
| Message-ID: | CAOR=d=1Km2OP7eJbY9-RCefa2C0jhVe+Z87KjdhsdzsrAQQr6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Sep 19, 2011 at 10:28 PM, Anibal David Acosta <aa(at)devshock(dot)com> wrote:
> I have a lot of wasted bytes in some tables.
>
> Somewhere I read that maybe auto-vacuum can’t release space due to a low
> max_fsm_pages setting.
It's no longer there, as fsm was moved from memory (which was limited
by max fsm pages) to disk, which is limited by the size of your disks.
Most likely you aren't vacuuming aggresively enough. Lower
autovacuum_vacuum_cost_delay and raise autovacuum_vacuum_cost_limit,
and possibly raise max threads for vacuum works (forget the name)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2011-09-20 05:04:56 | Re: Postgres INSERT performance and scalability |
| Previous Message | Anibal David Acosta | 2011-09-20 04:28:43 | where is max_fsm_pages in PG9.0? |