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@xxxxxxxxxxxxxxxxxxxxx> 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
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
