From: | Vick Khera <vivek(at)khera(dot)org> |
---|---|
To: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: number of page slots needed (1576544) exceeds max_fsm_pages (204800)] |
Date: | 2010-01-18 19:43:11 |
Message-ID: | 2968dfd61001181143n3338036bwf703dfd6b92d99f5@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jan 18, 2010 at 1:47 PM, Reid Thompson <reid(dot)thompson(at)ateb(dot)com> wrote:
> Does this max_fsm_pages value seem OK for a 46GB database?
> I've clustered all the tables that seemed to be exhibiting large amounts
> of bloat.
My big DB is about 70 on disk. I have fsm pages set to 3.4 million,
and occasionally that gets overrun. It is nearly catastrophic to us
when that happens as performance takes a serious nose dive. This is
probably the major reason switching to 8.4 is high on our list. Our
DB has a *lot* of data churn, and that makes a lot of pages with space
on them to track.
One more thing you may wish to consider is running re-index on your
tables. I found that a lot of pages with empty space were compacted
and the number of fsm entries went down significantly when I did this
last week. For me this was more important than running cluster to
pack the data tables themselves.
From | Date | Subject | |
---|---|---|---|
Next Message | Reid Thompson | 2010-01-18 19:49:52 | Re: number of page slots needed (1576544) exceeds max_fsm_pages (204800)] |
Previous Message | Bob Pawley | 2010-01-18 19:31:57 | Updating from a column |