On Tue, Aug 4, 2009 at 9:05 AM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> Lonni J Friedman <netllama@gmail.com> writes:
>> I have a postgresql 8.1.10 instance running on Linux. When vacuumdb
>> runs, I see the following in the server log:
>
>> 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".
>> LOG: max_fsm_relations(1000) equals the number of relations checked
>
>> What is puzzling, is where its getting that 1000 from, as in
>> postgresql.conf, I have:
>> max_fsm_relations = 2000
>
>> I've restarted the server (several times, in fact) since setting
>> max_fsm_relations=2000, so I can't figure out why its still using
>> 1000. Is there some alternate location that it might be getting set?
>
> Sounds to me like you're editing the wrong config file. Have you
> checked "show config_file" to see what the postmaster thinks it's
> using?
show config_file ;
config_file
-------------------------------------
/var/lib/pgsql/data/postgresql.conf
(1 row)
$ grep max_fsm_relations /var/lib/pgsql/data/postgresql.conf
#max_fsm_pages = 20000 # min max_fsm_relations*16, 6 bytes each
#max_fsm_relations = 1500 # min 100, ~70 bytes each
max_fsm_relations = 2000
That's the file that I thought it should have been using. Is there a
way to dynamically change the value from within psql?
