Re: max_fsm_relations question

From: Bill Moran <wmoran(at)collaborativefusion(dot)com>
To: "Kynn Jones" <kynnjo(at)gmail(dot)com>
Cc: "pgsql-general General" <pgsql-general(at)postgresql(dot)org>
Subject: Re: max_fsm_relations question
Date: 2008-08-05 17:36:23
Message-ID: 20080805133623.11d1a64c.wmoran@collaborativefusion.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

In response to "Kynn Jones" <kynnjo(at)gmail(dot)com>:

> Hi. I have a database that is created and populated by a Perl script.
> (FWIW, the size of this database is about 12GB, according to
> pg_database_size()).
>
> If, right after the database is built, I connect to it and manually run
> VACUUM ANALYZE, I get 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".
>
> I find this puzzling because the database has only 120 relations.

How many other databases do you have on that server? fsm_relations has
to track all relations in all databases.

> Is there a way I can structure the populating of the database to get rid of
> this message? E.g. would it help to have the script run VACUUM after it
> populates each new table?

No. If that parameter is too low you need to raise it, period.

--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran(at)collaborativefusion(dot)com
Phone: 412-422-3463x4023

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Harshad Pethe 2008-08-05 18:15:49 Installation problem ~!
Previous Message Kynn Jones 2008-08-05 17:16:12 max_fsm_relations question