Postgres monitoring tool check_postgres version 2.8.0

http://bucardo.org/check_postgres/

I'm happy to announce that version 2.8.0 of check_postgres has now been
released. This version adds internationalization support, many bug fixes and
enhancements, a complete test suite, and four new actions:

disabled_triggers: checks on the number of disabled triggers in the database.
Triggers can be disabled with an ALTER TABLE command, but for most cases this
should be a very temporary event.

prepared_txns: checks on the maximum age of any prepared transactions. The use
of these is very rare, and is only associated with two-part commit, so for most
installations seeing a prepared transaction indicates a problem that should be
fixed. Unclosed prepared transactions, like an open regular transaction, will
prevent vacuum from doing its job completely.

new_version_cp: checks if the version of check_postgres you are running is the
latest one available. Versions consist of three numbers: major, minor, and
revision. If a minor revision is available, a warning is given. If a major or
minor upgrade is available, a critical is given.

new_version_pg: checks is a newer version of Postgres is available. This only
checks the revision, so that if you are running 8.1.11, it will warn you that a
newer version in the 8.1 series is available, and not bug you about 8.3.

Special thanks to the French translators: all messages are now available in
French if your environment variable (LC_ALL, LC_MESSAGES, or LC_ALL) is set to
'fr'. Other language translations are needed - patches welcome!

This version also has a complete infrastructure around it, rather than a simple
Perl script. Thus, the correct procedure for installing is to download and
unpack the tarball, and then run:

perl Makefile.PL
make
make test
make install

The tests are very important, and it is highly encouraged that everyone using
check_postgres run the tests on their system to help flush out any problems. If
the tests do not pass for you, please send an email to check_postgres@nagios.org
describing the problem. Note that you may need to set the environment variable
PGBINDIR if the Postgres utilities are not in your path. The tests need initdb,
pg_ctl, pg_controldata, and psql.

--
Greg Sabino Mullane greg@endpoint.com
End Point Corporation
PGP Key: 0x14964AC8