| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Adam Radłowski <adamr(at)informatyka(dot)gdansk(dot)pl> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: max_fsm_relations |
| Date: | 2008-11-30 17:51:22 |
| Message-ID: | 16624.1228067482@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
=?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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Radłowski | 2008-11-30 19:52:25 | Re: max_fsm_relations |
| Previous Message | Igniris Valdivia Baez | 2008-11-30 15:10:22 | I want to unsubscribe me from this list |