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.
IIRC, I was the one wanting it to get into server logs at
default log settings; since I found it most useful at catching
the too low FSM settings in a regularly scheduled vacuum;
and if I recall, the previous output about FSM space never
ended up in log files unless you set the level to something
quite verbose.
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.
Actually there's something else I wanted to bring up regarding
this "feature" - now that autovacuum's around; the only reason I
still have a scheduled database-wide-vacuum is for this FSM message.
If there's a way of getting the info without doing the vacuum,
(i.e. was a pg_* view created that lets me see it?) I'll be even
happier to withdraw that request.
Ron M
