Skip site navigation (1) Skip section navigation (2)

Re: max_fsm_relations

From: Adam Radłowski <adamr(at)informatyka(dot)gdansk(dot)pl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: max_fsm_relations
Date: 2008-11-30 19:52:25
Message-ID: 4932EEF9.60603@informatyka.gdansk.pl (view raw or flat)
Thread:
Lists: pgsql-admin
So, are You suggesting, that at the time of full database vacuuming, 
some of tables are not vacuumed, when "max_fsm_relations" is to small ?
Thanks for Your fast answer.
Adam

Tom Lane pisze:
> =?ISO-8859-2?Q?Adam_Rad=B3owski?= <adamr(at)informatyka(dot)gdansk(dot)pl> writes:
>> PostgreSQL 8.1.3 (windows), 8.1.9 - 8.1.10 (linux).
>> I have databases, what are vacuumed using cron very regularry (vacuumdb 
>> -a -f ...) and I know when should do this. Automatic vacuuming is off. 
>> There are thousands of tables in one cluster (for ex. 10000). If I do 
>> vacuuming manually, I can see the warning:
>> NOTICE:  max_fsm_relations(1000) equals the number of relations checked
>> HINT:  You have at least 1000 relations.  Consider increasing the 
>> configuration parameter "max_fsm_relations".
>> But all is working properly.
> 
> Only for small values of "properly".  You will be seeing table bloat
> over time if you don't make the FSM large enough.
> 
> 			regards, tom lane
> 

In response to

Responses

pgsql-admin by date

Next:From: Alvaro HerreraDate: 2008-12-01 13:17:31
Subject: Re: max_fsm_relations
Previous:From: Tom LaneDate: 2008-11-30 17:51:22
Subject: Re: max_fsm_relations

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group