Re: number of page slots needed (1576544) exceeds max_fsm_pages (204800)]
От | Vick Khera |
---|---|
Тема | Re: number of page slots needed (1576544) exceeds max_fsm_pages (204800)] |
Дата | |
Msg-id | 2968dfd61001181143n3338036bwf703dfd6b92d99f5@mail.gmail.com обсуждение исходный текст |
Ответ на | number of page slots needed (1576544) exceeds max_fsm_pages (204800)] (Reid Thompson <reid.thompson@ateb.com>) |
Ответы |
Re: number of page slots needed (1576544) exceeds
max_fsm_pages (204800)]
Re: number of page slots needed (1576544) exceeds max_fsm_pages (204800)] |
Список | pgsql-general |
On Mon, Jan 18, 2010 at 1:47 PM, Reid Thompson <reid.thompson@ateb.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.
В списке pgsql-general по дате отправления: