Susan Russo wrote:
Hi Tom - thanks for the additional/confirming info.
So you definitely have got a problem of needing more vacuuming...
Yes, we're going to nightly, as I said in last message, however,
it worse than this.
I found that *1* vacuum analyze works well in many insta
ests=AWL,BAYES_50,SPF_HELO_PASS
autolearn=unavailable version=3.1.4
X-Spam-Level:
To: Susan Russo <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED], pgsql-performance@postgresql.org
Subject: Re: [PERFORM] does VACUUM ANALYZE complete with this error?
Comments: In-reply-to Susan Russo <
Susan Russo <[EMAIL PROTECTED]> writes:
>> What PG version is that? I recall we fixed a problem recently that
>> caused the requested max_fsm_pages to increase some more when you'd
>> increased it to what the message said.
> 8.1.4
OK, I checked the CVS history and found this:
2006-09-21 16:31
;
cc: pgsql-performance@postgresql.org, [EMAIL PROTECTED]
Subject: Re: [PERFORM] does VACUUM ANALYZE complete with this error?
Comments: In-reply-to Susan Russo <[EMAIL PROTECTED]>
message dated "Wed, 23 May 2007 09:26:54 -0400"
Date: Wed, 23 May 2007 10:01:06 -0400
From: To
On May 23, 2007, at 9:26 AM, Susan Russo wrote:
I've played 'catch up' wrt adjusting max_fsm_pages (seems to be a
regular event),
however am wondering if the vacuum analyze which reports the error was
actually completed?
Yes, it completed. However not all pages with open space in them are
Susan Russo <[EMAIL PROTECTED]> writes:
> We're seeing these type of error messages:
> NOTICE: number of page slots needed (237120) exceeds max_fsm_pages (12)
> HINT: Consider increasing the configuration parameter "max_fsm_pages" to a
> value over 237120.
> vacuumdb: vacuuming database "fb
Hi,
We're seeing these type of error messages:
NOTICE: number of page slots needed (237120) exceeds max_fsm_pages (12)
HINT: Consider increasing the configuration parameter "max_fsm_pages" to a
value over 237120.
vacuumdb: vacuuming database "fb_2007_01_17"
I've played 'catch up' wrt adj
