From: Greg Sabino Mullane Date: Wed, 7 Apr 2010 15:45:40 +0000 (-0400) Subject: Bump to version 2.15.0, regenerate HTML, update release changes. X-Git-Tag: 2.15.1~48^2~2 X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=ba324843d54fd2a00198d78001069983f74725e6;p=check_postgres.git Bump to version 2.15.0, regenerate HTML, update release changes. --- diff --git a/META.yml b/META.yml index 212168bc9..ab76206bd 100644 --- a/META.yml +++ b/META.yml @@ -1,6 +1,6 @@ --- #YAML:1.0 name : check_postgres.pl -version : 2.14.4 +version : 2.15.0 abstract : Postgres monitoring script author: - Greg Sabino Mullane @@ -30,7 +30,7 @@ recommends: provides: check_postgres: file : check_postgres.pl - version : 2.14.4 + version : 2.15.0 keywords: - Postgres diff --git a/Makefile.PL b/Makefile.PL index 8b7cf5415..28d2130d1 100644 --- a/Makefile.PL +++ b/Makefile.PL @@ -6,7 +6,7 @@ use strict; use warnings; use 5.006001; -my $VERSION = '2.14.4'; +my $VERSION = '2.15.0'; if ($VERSION =~ /_/) { print "WARNING! This is a test version ($VERSION) and should not be used in production!\n"; diff --git a/check_postgres.pl b/check_postgres.pl index f6fb0ce94..40cb89093 100755 --- a/check_postgres.pl +++ b/check_postgres.pl @@ -8454,9 +8454,14 @@ Items not specifically attributed are by Greg Sabino Mullane. =over 4 -=item B +=item B Add --man option to show the entire manual. (Andy Lester) + +=item B + + Redo the internal run_command() sub to use -x and hashes instead of regexes. + Fix error in custom logic (Andreas Mager) Add the "pgbouncer_checksum" action (Guillaume Lelarge) Fix regex to work on WIN32 for check_fsm_relations and check_fsm_pages (Luke Koops) Don't apply a LIMIT when using --exclude on the bloat action (Marti Raudsepp) diff --git a/check_postgres.pl.html b/check_postgres.pl.html index b3a4eaada..3402c53be 100644 --- a/check_postgres.pl.html +++ b/check_postgres.pl.html @@ -62,6 +62,7 @@
  • new_version_cp
  • new_version_pg
  • new_version_bc
    • +
  • pgbouncer_checksum
  • prepared_txns
  • query_runtime
  • query_time
    • @@ -105,7 +106,7 @@

    NAME

    check_postgres.pl - a Postgres monitoring script for Nagios, MRTG, Cacti, and others

    -

    This documents describes check_postgres.pl version 2.14.4

    +

    This documents describes check_postgres.pl version 2.15.0

    @@ -518,10 +519,10 @@ times larger the relation is compared to how large it should be), just pass in <

    checkpoint

    (symlink: check_postgres_checkpoint) Determines how long since the last checkpoint has -been run. This must run on the same server as the database that is being checked. This check is -meant to run on a "warm standby" server that is actively processing shipped WAL files, and is meant -to check that your warm standby is truly 'warm'. The data directory must be set, either by the -environment variable PGDATA, or passing +been run. This must run on the same server as the database that is being checked (e.g. the -h +flag will not work). This check is meant to run on a "warm standby" server that is actively +processing shipped WAL files, and is meant to check that your warm standby is truly 'warm'. +The data directory must be set, either by the environment variable PGDATA, or passing the --datadir argument. It returns the number of seconds since the last checkpoint was run, as determined by parsing the call to pg_controldata. Because of this, the pg_controldata executable must be available in the current path. Alternatively, you can @@ -542,7 +543,8 @@ Takes no --warning or --critical options.

    (symlink: check_postgres_custom_query) Runs a custom query of your choosing, and parses the results. The query itself is passed in through the custom_query argument, and should be kept as simple as possible. If at all possible, wrap it in a view or a function to keep things easier to manage. The query should return one or two columns: the first -is the result that will be checked, and the second is any performance data you want sent.

    +is the result that will be checked, and the second is any performance data you want sent. They must be returned +as columns named result and data.

    At least one warning or critical argument must be specified. What these are set to depends on the type of query you are running. There are four types of custom_queries that can be run, specified by the valtype argument. If none is specified, this action defaults to 'integer'. The four types are:

    @@ -957,6 +959,27 @@ replication system for Postgres: see http://bucardo See also the information on the --get_method option.

    +

    pgbouncer_checksum

    +

    (symlink: check_postgres_pgbouncer_checksum) Checks that all the +pgBouncer settings are the same as last time you checked. +This is done by generating a checksum of a sorted list of setting names and +their values. Note that you shouldn't specify the database name, it will +automatically default to pgbouncer. Either the --warning or the --critical option +should be given, but not both. The value of each one is the checksum, a +32-character hexadecimal value. You can run with the special --critical=0 option +to find out an existing checksum.

    +

    This action requires the Digest::MD5 module.

    +

    Example 1: Find the initial checksum for pgbouncer configuration on port 6432 using the default user (usually postgres)

    +
    +  check_postgres_pgbouncer_checksum --port=6432 --critical=0
    +

    Example 2: Make sure no settings have changed and warn if so, using the checksum from above.

    +
    +  check_postgres_pgbouncer_checksum --port=6432 --warning=cd2f3b5e129dc2b4f5c0f6d8d2e64231
    +

    For MRTG output, returns a 1 or 0 indicating success of failure of the checksum to match. A +checksum must be provided as the --mrtg argument. The fourth line always gives the +current checksum.

    +

    +

    prepared_txns

    (symlink: check_postgres_prepared_txns) Check on the age of any existing prepared transactions. Note that most people will NOT use prepared transactions, as they are part of two-part commit @@ -1461,11 +1484,18 @@ feature requests, and commit notices, send email to HISTORY

    Items not specifically attributed are by Greg Sabino Mullane.

    -
    Version 2.14.4
    +
    Version 2.15.0
    -  Fix to show database properly when using slony_status (Guillaume Lelarge)
    + Redo the internal run_command() sub to use -x and hashes instead of regexes. + Fix error in custom logic (Andreas Mager) + Add the "pgbouncer_checksum" action (Guillaume Lelarge) + Fix regex to work on WIN32 for check_fsm_relations and check_fsm_pages (Luke Koops) + Don't apply a LIMIT when using --exclude on the bloat action (Marti Raudsepp) + Change the output of query_time to show pid,user,port, and address (Giles Westwood) + Fix to show database properly when using slony_status (Guillaume Lelarge) + Allow warning items for same_schema to be comma-separated (Guillaume Lelarge)
    Version 2.14.3 (March 1, 2010)