Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
max_fsm_relations
- From: "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com>
- To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
- Subject: max_fsm_relations
- Date: Fri, 27 Feb 2009 12:37:03 -0700
- Message-id: <482E80323A35A54498B8B70FF2B8798003ED1B9866@azsmsx504.amr.corp.intel.com> <text/plain>
I just did a Vacuum Analyze on a DB. It worked OK, but I got... 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 browsed around and learned that this has to do with keeping track of free disk space. Q: Is there a problem with leaving this alone? How serious is this if it is a problem? Q: Is there a way I can shrink this number (reload the data to consume the free space perhaps?) Thanks -dave
- Follow-Ups:
- Re: max_fsm_relations
- From: Bill Moran
- Re: max_fsm_relations
- From: Joshua D. Drake
- Re: max_fsm_relations
- Prev by Date: Re: strange performance problem
- Next by Date: Re: max_fsm_relations
- Previous by thread: Hiding row counts in psql
- Next by thread: Re: max_fsm_relations
- Indexes: