[check_postgres] [PATCH] Change autovac_freeze default warn/critical from 90%/95% to 105%/120%

[Marti Raudsepp]

On Wed, Feb 17, 2010 at 1:41 AM, Robert Treat
<xzilla at users.sourceforge.net> wrote:
> The logic behind this change is flawed. If your database reaches the
> autovac_max_freeze, you are susceptible to a large performance degradation due
> to increased i/o load from your database maxing out autovac workers whilst
> trying to catch up on vacuuming. For most people, advance notice of that
> threshold allows them flexibility to spread out the vacuuming over time, adjust
> the vacuum cost params, or schedule vacuuming for low server activity times;
> if you set your warning/critical above 100% it's already too late.

Thank you, this makes sense. And I was wondering why Nagios kept
nagging at me even though my DB was working as designed.

Goes to show that the purpose of checks should also be documented, not
just how they work.

Regards,
Marti