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 ED63A9FA3B3 for ; Mon, 15 May 2006 12:16:49 -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 97746-03 for ; Mon, 15 May 2006 12:16:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 285059FA226 for ; Mon, 15 May 2006 12:16:36 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 6A6CF56427; Mon, 15 May 2006 10:16:36 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Mon, 15 May 2006 10:16:36 -0500 Date: Mon, 15 May 2006 10:16:36 -0500 From: "Jim C. Nasby" To: Gourish Singbal Cc: "pgsql-admin@postgresql.org" Subject: Re: increasing max_fsm_pages. Message-ID: <20060515151635.GF26212@pervasive.com> References: <674d1f8a0605142348nf3dce9bl69d5f1896444ad4f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <674d1f8a0605142348nf3dce9bl69d5f1896444ad4f@mail.gmail.com> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060515:gourish@gmail.com::5Qhum1FGG3TELysc:00000000000000000000 0000000000000000000000000fow X-Hashcash: 1:20:060515:pgsql-admin@postgresql.org::24X0VJvFOlik5acZ:00000000000 0000000000000000000000003ZQW X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/181 X-Sequence-Number: 21713 On Mon, May 15, 2006 at 12:18:50PM +0530, Gourish Singbal wrote: > 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 ?. I'd say more accurately it'll be at stake if you don't. Each page slot takes 6 bytes, so you'll be using an additional 600k, which is essentially nothing. This article was written using the older vacuum output, but it might still be informative for you: http://www.pervasivepostgres.com/lp/newsletters/2005/Insights_opensource_Nov.asp#3 -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461