>>> On Tue, Nov 28, 2006 at 3:37 PM, in message
<456CAC0E.3090409@cheapcomplexdevices.com>, Ron Mayer
<rm_pg@cheapcomplexdevices.com> wrote:
> Tom Lane wrote:
>> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>>> One exceedingly minor logging issue I just noticed in looking at
the log
>>> from a beta3.
>>
>> Yeah, this is someone's idea of a feature:
>>
>> CheckFreeSpaceMapStatistics(NOTICE, numRels, needed);
>> /* Print to server logs too because is deals with a config
variable. */
>> CheckFreeSpaceMapStatistics(LOG, numRels, needed);
>>
>> I thought it was a crock when it was put in, but lost the argument.
>
> If there's a better way for me to be managing this, let me know
> and I'll happily withdraw my requests that the message be spewed
> twice.
I've generally been capturing the output of my nightly VACUUM ANALYZE
VERBOSE run, and looking for this information at the end of that file.
> the only reason I
> still have a scheduled database- wide- vacuum is for this FSM
message.
Isn't it necessary to do this periodically to prevent transaction ID
wraparound?
-Kevin