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 040FF9FA19B for ; Mon, 15 May 2006 13:25:36 -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 05081-08 for ; Mon, 15 May 2006 13:25:24 -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 5F1239F944D for ; Mon, 15 May 2006 13:25:24 -0300 (ADT) Received: by nz-out-0102.google.com with SMTP id 13so170930nzn for ; Mon, 15 May 2006 09:25:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ChvQi1OYfJvTtAp9tBbfUCp19kGiQPA5eTBVXuFNcm0u76jNR6ZJ7r58RGYAWVe3MQKOyObIWyinEYAtPBoGNke32kwtt+LRe7xNItVhSdUbTxA8LdrAlmpQNQJOUI0RAXS869jJ1OUdbMTMoQ/wagKSU7BQZnuMZiFN7ApfyV0= Received: by 10.36.139.7 with SMTP id m7mr1667808nzd; Mon, 15 May 2006 09:25:23 -0700 (PDT) Received: by 10.36.74.15 with HTTP; Mon, 15 May 2006 09:25:23 -0700 (PDT) Message-ID: <674d1f8a0605150925q7f9b01b7k736fbe266f8b050e@mail.gmail.com> Date: Mon, 15 May 2006 21:55:23 +0530 From: "Gourish Singbal" To: "pgsql-admin@postgresql.org" Subject: Re: increasing max_fsm_pages. In-Reply-To: <20060515151635.GF26212@pervasive.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_16972_20151206.1147710323139" References: <674d1f8a0605142348nf3dce9bl69d5f1896444ad4f@mail.gmail.com> <20060515151635.GF26212@pervasive.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/187 X-Sequence-Number: 21719 ------=_Part_16972_20151206.1147710323139 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Thanks a lot for the information . We have modified the postgresql.conf fil= e to have max_fsm_pages to 300000. And restarted the database after doing a Vacuum Full . INFO: free space map contains 11518 pages in 56 relations DETAIL: A total of 12320 page slots are in use (including overhead). 12320 page slots are required to track all free space. Current limits are: 300000 page slots, 500 relations, using 1812 KB. VACUUM On 5/15/06, Jim C. Nasby wrote: > > 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 > --=20 Best, Gourish Singbal ------=_Part_16972_20151206.1147710323139 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
 
Thanks a lot for the information . We have modified the postgresq= l.conf file to have max_fsm_pages to 300000. And restarted the database aft= er doing a Vacuum Full .
 
INFO:  free space map contains 11518 pages in 56 relations
DET= AIL:  A total of 12320 page slots are in use (including overhead).
= 12320 page slots are required to track all free space.
Current limits ar= e:  300000 page slots, 500 relations, using 1812 KB.
VACUUM
 

 
On 5/15/06, = Jim C. Nasby <jnasby@pervasi= ve.com> wrote:
On Mon, May 15, 2006 at 12:18:50= PM +0530, Gourish Singbal wrote:
> Group.
>
> Need some h= elp 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 :-
> IN= FO:  free space map contains 195236 pages in 72 relations
>= DETAIL:  A total of 200000 page slots are in use (including over= head).
> 201744 page slots are required to track all free space.
> Cu= rrent limits are:  200000 page slots, 500 relations, using 1226 K= B.
> NOTICE:  number of page slots needed (201744) exceeds = max_fsm_pages (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 ?.

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 nothi= ng.

This article was written using the older vacuum output, but it migh= t
still be informative for you:
http://www.pervas= ivepostgres.com/lp/newsletters/2005/Insights_opensource_Nov.asp#3
--
Jim C. Nasby, Sr. Engineering Consultant   &nb= sp;  jnasby@pervasive.com=
Pervasive Software      http://pervasive.com    work: 5= 12-231-6117
vcard: http://jim.nasby.= net/pervasive.vcf       cell: 512-569-946= 1



--
Best,
Gourish S= ingbal=20 ------=_Part_16972_20151206.1147710323139--