Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: max_fsm_relations


  • From: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
  • To: "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com>
  • Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
  • Subject: Re: max_fsm_relations
  • Date: Fri, 27 Feb 2009 11:56:50 -0800
  • Message-id: <1235764610.1879.1.camel@jd-laptop.pragmaticzealot.org> <text/plain>

On Fri, 2009-02-27 at 12:37 -0700, Gauthier, Dave wrote:
> 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?)

This is "relations" which means tables, indexes etc... So unless you
start dropping things, no you can't reduce it.

Just increase it a bit (say 20%) it won't hurt you.

Note it does use a little shared_memory,.

Joshua D. Drake


> 
>  
> 
> Thanks
> 
> -dave
> 
>  
> 
> 
-- 
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
   Consulting, Development, Support, Training
   503-667-4564 - http://www.commandprompt.com/
   The PostgreSQL Company, serving since 1997




Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group