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

Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org
Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.
Date: 2005-02-24 09:26:24
Message-ID: 421D9DC0.5070707@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-patches
>   I find this tiny (9-line) patch useful to help my clients know 
>   when FSM settings may need updating.
> 
> Some of the more frequently asked questions here are in regards to FSM
> settings.  One hint I've seen is to run "vacuum verbose;".  At the end 
> of thousands of lines of INFO and DETAIL messages vacuum verbose has 2
> separate lines with some numbers to compare ("total pages needed" and 
> "FSM size...pages") that help indicate too low fsm settings.
> 
> 
> I've gotten into the habit of always installing the following patch
> (below) that automatically does this comparison for me, and if
> max_fsm_pages is too small, it logs a warning as shown here:
> 
>  patched=# vacuum;
>  WARNING:  max_fsm_pages(1601) is smaller than total pages needed(2832)
>  VACUUM

I think this patch is great.  I can never figure out how to set those 
settings easily.

Chris

In response to

pgsql-patches by date

Next:From: Simon RiggsDate: 2005-02-24 13:24:51
Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.
Previous:From: Ron MayerDate: 2005-02-24 08:49:36
Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.

pgsql-general by date

Next:From: mefDate: 2005-02-24 10:42:39
Subject: racing of tables deleting - how?
Previous:From: Sebastien FLAESCHDate: 2005-02-24 08:56:45
Subject: Suggestion for parameterized queries

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group