pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gourish Singbal <gourish@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: increasing max_fsm_pages.
Date: Mon, 15 May 2006 21:55:23 +0530
Message-ID: <674d1f8a0605150925q7f9b01b7k736fbe266f8b050e@mail.gmail.com> (raw)
In-Reply-To: <20060515151635.GF26212@pervasive.com>
References: <674d1f8a0605142348nf3dce9bl69d5f1896444ad4f@mail.gmail.com>
	<20060515151635.GF26212@pervasive.com>

Thanks a lot for the information . We have modified the postgresql.conf file
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 <jnasby@pervasive.com> 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
>



-- 
Best,
Gourish Singbal

view thread (4+ messages)  latest in thread

Message-ID: <674d1f8a0605150925q7f9b01b7k736fbe266f8b050e@mail.gmail.com>
Permalink:  ../674d1f8a0605150925q7f9b01b7k736fbe266f8b050e@mail.gmail.com/
Also on:    postgresql.org/message-id/674d1f8a0605150925q7f9b01b7k736fbe266f8b050e@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: gourish@gmail.com
  Subject: Re: increasing max_fsm_pages.
  In-Reply-To: <674d1f8a0605150925q7f9b01b7k736fbe266f8b050e@mail.gmail.com>
  References: <674d1f8a0605142348nf3dce9bl69d5f1896444ad4f@mail.gmail.com> <20060515151635.GF26212@pervasive.com> <674d1f8a0605150925q7f9b01b7k736fbe266f8b050e@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