| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: max_fsm_pages >800k ... ? |
| Date: | 2005-06-16 05:10:24 |
| Message-ID: | 10677.1118898624@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
> Without more information to provide at this time, does the following seem
> "unusual"?
> INFO: free space map: 252 relations, 411494 pages stored; 738640 total pages needed
> DETAIL: Allocated FSM size: 2000 relations + 400000 pages = 2463 kB shared memory.
What this is saying is that you'd need 738640 fsm_pages slots to
remember every single page that has a useful amount of free space.
However, you don't necessarily have to remember all those pages.
If you remember enough pages to satisfy insert/update requests
until the next VACUUM happens, then you're good.
I think the bottom-line question is "are you seeing any database
bloat?" If yes, increase max_fsm_pages; if no, worry not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-06-16 05:10:36 | Re: [HACKERS] INHERITS and planning |
| Previous Message | Rod Taylor | 2005-06-16 05:08:18 | Re: Escape handling in strings |