[check_postgres] a check for hitting autovacuum_max_freeze_age?

[Greg Sabino Mullane]

> the one thing i am thinking about is, is it enough to just compare the
> age of each database to max_freeze_age, and toss a warning if you get
> within say 10% of it.  or would it be better to make a smart check that
> would count the number of tables this would affect, and return a
> warning/critical based on the number of tables.  if we went that route,
> youd need to run the check once for each database, is that a problem? 

I don't know that the number of tables would really matter that much - if
you are close, you probably want a warning no matter what. 

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
Url : https://mail.endcrypt.com/pipermail/check_postgres/attachments/20080715/ffc14bc8/signature.bin