Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 9CB669FB416 for ; Mon, 2 Apr 2007 06:55:51 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 98043-04 for ; Mon, 2 Apr 2007 06:55:42 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246]) by postgresql.org (Postfix) with ESMTP id 075D29FB2AB for ; Mon, 2 Apr 2007 06:55:45 -0300 (ADT) Received: by an-out-0708.google.com with SMTP id c24so1206272ana for ; Mon, 02 Apr 2007 02:55:45 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=VBjKnZqC2+uh9XCEqjMJFNNLghFsxZ5kFxKwvjg/vrZsDK6onSwUVfSD1wukPfo9Usbt87AbydTvIhyX+v1DbpT43YKHj+GlcOnVfSGhguXfV1/WdQAjwKn1dA/R57wt5Rs7kr+vXvOTz7Wcgayxsn0E2OgXc/h1KwU8JV8V/hY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=f8r7w4gDcHTE9acoyZnZbwRjvqnJAqKx/PQKqZ09VyxGgUltzwVFRRLZe6tneI+2qn4fr/o5l95FfNRWwBodPIEq5DvvjGXCz1xc6kdqL5Gua3BA5ZqBkcuLv765RkLCYudba5QXLANe2TLejFyzhQgl5ZOThF10cfLQ7kkuvpQ= Received: by 10.100.9.19 with SMTP id 19mr3340590ani.1175507744878; Mon, 02 Apr 2007 02:55:44 -0700 (PDT) Received: by 10.100.14.1 with HTTP; Mon, 2 Apr 2007 02:55:44 -0700 (PDT) Message-ID: Date: Mon, 2 Apr 2007 14:55:44 +0500 From: "Shoaib Mir" To: "Abu Mushayeed" Subject: Re: max_fsm_pages Cc: pgsql-admin@postgresql.org In-Reply-To: <718991.89112.qm@web57102.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_83591_10133651.1175507744638" References: <718991.89112.qm@web57102.mail.re3.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/8 X-Sequence-Number: 25072 ------=_Part_83591_10133651.1175507744638 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 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 alertswith the free Yahoo! > Toolbar. > > ------=_Part_83591_10133651.1175507744638 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 with the free Yahoo! Toolbar.


------=_Part_83591_10133651.1175507744638--