pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Shoaib Mir <shoaibmir@gmail.com>
To: Abu Mushayeed <abumushayeed@yahoo.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: max_fsm_pages
Date: Mon, 2 Apr 2007 14:55:44 +0500
Message-ID: <bf54be870704020255g424914e6r6015fb3968207933@mail.gmail.com> (raw)
In-Reply-To: <718991.89112.qm@web57102.mail.re3.yahoo.com>
References: <718991.89112.qm@web57102.mail.re3.yahoo.com>

First of all run the VACUUM FULL ANALYZE and that should hopefully help you
get rid of this problem without changing the max_fsm_pages. Other then this
I will recommend you to have the autovacuuming process in place for proper
database maintenance.

--
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 4/1/07, Abu Mushayeed <abumushayeed@yahoo.com> wrote:
>
> PG DB: 8.1.3
> 12 DB in the cluster
>
> When I do a full vacuum of the database cluster, at the end I am getting
> the message as follows:
>
> psql:dba_task.sql:1: INFO:  free space map contains 8033993 pages in 1023
> relations
> DETAIL:  A total of 8000000 page slots are in use (including overhead).
> 8201952 page slots are required to track all free space.
> Current limits are:  8000000 page slots, 32768 relations, using 49054 KB.
> psql:dba_task.sql:1: NOTICE:  number of page slots needed (8201952)
> exceeds max_fsm_pages (8000000)
> HINT:  Consider increasing the configuration parameter "max_fsm_pages" to
> a value over 8201952.
>
> My questions are:
>
> 1. With out increasing the max_fsm_pages, can I bring down the need for
> fsm_pages by deleting unnecessary tables?
> 2. As, the database grows the need for max_fsm_pages grows too, what is
> the best practice?
> 3. As a new postgres DBA, how should one manage this parameter?
>
> Thanks
> Abu Mushayeed
>
> ------------------------------
> It's here! Your new message!
> Get new email alerts<http://us.rd.yahoo.com/evt=49938/*http://tools.search.yahoo.com/toolbar/features/mail/>with the free Yahoo!
> Toolbar.
>
>

view thread (6+ messages)

Message-ID: <bf54be870704020255g424914e6r6015fb3968207933@mail.gmail.com>
Permalink:  ../bf54be870704020255g424914e6r6015fb3968207933@mail.gmail.com/
Also on:    postgresql.org/message-id/bf54be870704020255g424914e6r6015fb3968207933@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: shoaibmir@gmail.com, abumushayeed@yahoo.com
  Subject: Re: max_fsm_pages
  In-Reply-To: <bf54be870704020255g424914e6r6015fb3968207933@mail.gmail.com>
  References: <718991.89112.qm@web57102.mail.re3.yahoo.com> <bf54be870704020255g424914e6r6015fb3968207933@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox