From: Tom Lane <tgl@sss.pgh.pa.us>
To: Colton A Smith <smith@cs.utk.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: fsm allocation
Date: Fri, 18 Nov 2005 18:59:25 -0500
Message-ID: <13204.1132358365@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.62.0511170802030.29277@cetus5.cs.utk.edu>
References: <Pine.LNX.4.62.0511170802030.29277@cetus5.cs.utk.edu>
Colton A Smith <smith@cs.utk.edu> writes:
> Recently, I vacuumed and the output told me I had 47 relations, 151751
> pages stored, and that I needed 237680 total pages. My fsm allocation
> was for 1000 relations, 150000 pages.
> I took this to mean the vacuum didn't work and that I needed to allocate
> more pages. So I edited the conf file to allocate 300000 pages. After
> altering SHMMAX on my system, I was able to restart the database.
> I tried vacuuming again. This time, the output said I had 47
> relations, 301906 pages and that I now needed 333104 total pages.
> I'm confused. Does this mean I need to bump up my fsm allocation again?
I seem to recall that the FSM's threshold for how much free space is
worth remembering does vary with the number of slots it's got available,
so this increase isn't too surprising.
Without knowing anything about the total size of your database, it's
difficult to say whether these numbers are out of line or not.
regards, tom lane
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: tgl@sss.pgh.pa.us, smith@cs.utk.edu
Subject: Re: fsm allocation
In-Reply-To: <13204.1132358365@sss.pgh.pa.us>
References: <Pine.LNX.4.62.0511170802030.29277@cetus5.cs.utk.edu> <13204.1132358365@sss.pgh.pa.us>
* 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