Re: strange fsm issues

From: Jeff Frost <jeff(at)frostconsultingllc(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: strange fsm issues
Date: 2006-06-22 14:52:47
Message-ID: Pine.LNX.4.64.0606220750310.4350@discord.home.frostconsultingllc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, 21 Jun 2006, Jeff Frost wrote:

>> Current limits are: 100000 page slots, 2000 relations, using 713 KB.
>> NOTICE: number of page slots needed (102608) exceeds max_fsm_pages
>> (100000)
>> HINT: Consider increasing the configuration parameter "max_fsm_pages" to a
>> value over 102608.
>>
>> Unfortunately my screen back buffer didn't have the other vacuum verbose
>> outputs, so I had to pull the warnings out of the log file.
>>

So, I set it to 3366499. I came up with this number by:
select sum(relpages) from pg_class where relkind in ('r','t');
and adding that up for all the DBs (there is just the one plus postgres and
template1 and now I get th efollowing, so it appears this was actually a good
settings.

CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO: free space map contains 3339998 pages in 125 relations
DETAIL: A total of 3341600 page slots are in use (including overhead).
3341600 page slots are required to track all free space.
Current limits are: 3366499 page slots, 2000 relations, using 19853 KB.

So then the question is..why was vacuum suggesting such low settings
previously?

--
Jeff Frost, Owner <jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2006-06-22 15:40:08 Re: clustering takes too long!
Previous Message Andy Shellam 2006-06-22 14:31:38 Re: 2,2gb of pg_xlog ??