On Wed, Oct 15, 2008 at 11:29 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Decibel! <decibel@decibel.org> writes:
>> Since this is something that's not supposed to happen, making it a
>> WARNING might be appropriate too...
>
> Uh, the complaint was that the message is too noisy, not that it isn't
> noisy enough.
I think you're confusing the volume of the noise with the frequency of
the noise. Once a minute is too often to spit out a message like this
regardless of the log level, but at least at a higher log level
someone may have a better chance of noticing before the disk fills up.
A much better solution would be to not print the warning every time.
I think the right solution is to do exactly what you rejected
upthread, namely adding some kind of stack to track the last time this
was printed. It doesn't need to be real granular, or real exact.
Don't track each table separately, just add a static integer. If a
particular autovac run sees the problem at least once, increment the
integer and print out warnings for all tables found in that run if
(variable % 60) == 1.
...Robert
