From: | Vivek Khera <vivek(at)khera(dot)org> |
---|---|
To: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Calculation for Max_FSM_pages : Any rules of thumb? |
Date: | 2007-11-08 15:53:44 |
Message-ID: | A99C2241-71B1-451B-804E-F9B53412C720@khera.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Nov 1, 2007, at 8:51 PM, Ow Mun Heng wrote:
> Another question is, based on what I've read in the archives (in my
> laptop.. No-Inet conn @ work) Since I've overran my max_FSM, I'm
> basically screwed and will have to do a vacuum verbose FULL on the
> entire DB. Crap..
I've seen this repeated many times as well, and I can't think of a
really good reason why this should be true. Once you increase max fsm
pages, won't the very next regular vacuum find all the free space in
pages and add them to the map anyway? Ie, you've not "lost" any free
space once the next regular vacuum runs. At worst, you've got a
slightly bloated table because you allocated more pages rather than re-
using some, but is that worth a full vacuum? I don't think it will be
unless you're *way* under the fsm pages needed and have been for a
long time.
From | Date | Subject | |
---|---|---|---|
Next Message | Reg Me Please | 2007-11-08 15:59:25 | Re: what is the date format in binary query results |
Previous Message | Tom Lane | 2007-11-08 15:50:39 | Re: why there is no interval / interval operator? |