Re: Calculation for Max_FSM_pages : Any rules of thumb?

From: Ow Mun Heng <Ow(dot)Mun(dot)Heng(at)wdc(dot)com>
To: Bill Moran <wmoran(at)potentialtech(dot)com>
Cc: Vivek Khera <vivek(at)khera(dot)org>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Calculation for Max_FSM_pages : Any rules of thumb?
Date: 2007-11-13 06:37:24
Message-ID: 1194935844.8717.19.camel@neuromancer.home.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Thu, 2007-11-08 at 12:02 -0500, Bill Moran wrote:
> Frequently, when people ask for help because they've exceed max_fsm*,
> it's because they're not paying attention to their systems, and therefore
> the problem has been occurring for a while before it got so bad that
> they couldn't ignore it. As a result, a full vacuum is frequently a
> necessity.
>
> Folks who are monitoring their databases closely don't hit this
> problem nearly as often.
>

How does one monitor it closely anyway? the warning comes when one does
a vacuum verbose and with autovacuum turned on, I don't even see it
anywhere.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-11-13 07:21:54 Re: PQexec(), what should I do for the "NULL in command" problem?
Previous Message Albe Laurenz 2007-11-13 06:24:59 Re: Accessing a db with pgAdmin