X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 08B8D9F944D for ; Mon, 15 May 2006 03:49:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 30845-01 for ; Mon, 15 May 2006 03:48:51 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.207]) by postgresql.org (Postfix) with ESMTP id CBFD69F9430 for ; Mon, 15 May 2006 03:48:51 -0300 (ADT) Received: by nz-out-0102.google.com with SMTP id n1so2947nzf for ; Sun, 14 May 2006 23:48:50 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=N6OKcQXyFykqfG/HGqKUjHL09LzIkp6iM+FcSgj4qOAvaOmeJVE70Y4IEtS4syabUyJdG1486F1vKCcKCEaWkidCPwaQCHvM2mfD0I9y629oV3zHzGhoWP6jJlyr4F7MuQpSf6MNktYpy/gGuL03HIea6YavrRsP2PgfG9hICQ4= Received: by 10.36.148.1 with SMTP id v1mr5348083nzd; Sun, 14 May 2006 23:48:50 -0700 (PDT) Received: by 10.36.74.15 with HTTP; Sun, 14 May 2006 23:48:50 -0700 (PDT) Message-ID: <674d1f8a0605142348nf3dce9bl69d5f1896444ad4f@mail.gmail.com> Date: Mon, 15 May 2006 12:18:50 +0530 From: "Gourish Singbal" To: "pgsql-admin@postgresql.org" Subject: increasing max_fsm_pages. MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_9835_17232440.1147675730751" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/173 X-Sequence-Number: 21705 ------=_Part_9835_17232440.1147675730751 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Group. Need some help in understanding the tuning parameter. we got the below message on database wide vacuuming :- Vacuuming Result outcome on Sun May 14 20:22:47 PDT 2006 :- INFO: free space map contains 195236 pages in 72 relations DETAIL: A total of 200000 page slots are in use (including overhead). 201744 page slots are required to track all free space. Current limits are: 200000 page slots, 500 relations, using 1226 KB. NOTICE: number of page slots needed (201744) exceeds max_fsm_pages (200000= ) HINT: Consider increasing the configuration parameter "max_fsm_pages" to a value over 201744. VACUUM We have 4 GB of RAM on the machine if we increase the max_fsm_pages to 300000 will the database performance be at stake ?. http://www.varlena.com/GeneralBits/Tidbits/perf.html#maxfsmp --=20 Best, Gourish Singbal ------=_Part_9835_17232440.1147675730751 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Group.
 
Need some help in understanding the tuning parameter.
 
we got the below message on database wide vacuuming :-
Vacuuming Result outcome on Sun May 14 20:22:47 PDT 2006 :-
INFO:  free space map contains 195236 pages in 72 relations
DE= TAIL:  A total of 200000 page slots are in use (including overhead).201744 page slots are required to track all free space.
Current limits= are:  200000 page slots, 500 relations, using 1226 KB.
NOTICE:  number of page slots needed (201744) exceeds max_fsm_page= s (200000)
HINT:  Consider increasing the configuration parameter &= quot;max_fsm_pages" to a value over 201744.
VACUUM
 
We have 4 GB of RAM on the machine if we increase the max_fsm_pages to= 300000 will the database performance be at stake ?.
 
 
------=_Part_9835_17232440.1147675730751--