Skip site navigation (1)
Skip section navigation (2)
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 ?
Peripheral Links
Header And Logo
|
Site Navigation
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: Sun, 30 Nov 2008 20:52:25 +0100
- Message-id: <4932EEF9.60603@informatyka.gdansk.pl> <text/plain>
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 checkedHINT: 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
- References:
- max_fsm_relations
- From: Adam Radłowski
- Re: max_fsm_relations
- From: Tom Lane
- max_fsm_relations
- Prev by Date: Re: max_fsm_relations
- Previous by thread: Re: max_fsm_relations
- Next by thread: I want to unsubscribe me from this list
- Indexes: