Mention perflimit as a way to control the LIMIT in the bloat query.

diff --git a/check_postgres.pl b/check_postgres.pl
index 794a5119cd16486530a6496985adf9691a2cf0f0..88022bc71077f1a43db0d93ffeeb1e15f7ab47ec 100755 (executable)
--- a/check_postgres.pl
+++ b/check_postgres.pl
@@ -28,7 +28,7 @@ $Data::Dumper::Varname = 'POSTGRES';
 $Data::Dumper::Indent = 2;
 $Data::Dumper::Useqq = 1;
 
-our $VERSION = '2.2.2';
+our $VERSION = '2.2.3';
 
 use vars qw/ %opt $PSQL $res $COM $SQL $db /;
 
@@ -3453,7 +3453,7 @@ sub check_replicate_row {
 =head1 NAME
 
 B<check_postgres.pl> - a Postgres monitoring script for Nagios, MRTG, and others
-This documents describes check_postgres.pl version 2.2.2
+This documents describes check_postgres.pl version 2.2.3
 
 =head1 SYNOPSIS
 
@@ -3794,6 +3794,9 @@ before they can be considered by this test. If you really want to adjust these
 values, you can look for the variables I<$MINPAGES> and I<$MINIPAGES> at the top of the 
 C<check_bloat> subroutine.
 
+Only the top 10 most bloated relations are shown. You can change this number by 
+using the I<--perflimit> option to set your own limit.
+
 The schema named 'information_schema' is excluded from this test, as the only tables 
 it contains are small and do not change.
 
@@ -4566,6 +4569,10 @@ Items not specifically attributed are by Greg Sabino Mullane.
 
 =over 4
 
+=item B<Version 2.2.3>
+
+ Documentaion tweaks.
+
 =item B<Version 2.2.2> (September 30, 2008)
 
  Fixes for minor output and scoping problems.