Move archive_command docs around.

Greg Sabino Mullane · Greg Sabino Mullane · commit c48414cab4ba · 2010-12-28T10:46:31.000-05:00
diff --git a/check_postgres.pl b/check_postgres.pl
@@ -824,6 +824,7 @@ package check_postgres;
 ## Quick hash to put normal action information in one place:
 our $action_info = {
  # Name                 # clusterwide? # helpstring
+ archive_ready       => [1, 'Check the number of WAL files ready in the pg_xlog/archive_status'],
  autovac_freeze      => [1, 'Checks how close databases are to autovacuum_freeze_max_age.'],
  backends            => [1, 'Number of connections, compared to max_connections.'],
  bloat               => [0, 'Check for table and index bloat.'],
@@ -873,7 +874,6 @@ package check_postgres;
  txn_wraparound      => [1, 'See how close databases are getting to transaction ID wraparound.'],
  version             => [1, 'Check for proper Postgres version.'],
  wal_files           => [1, 'Check the number of WAL files in the pg_xlog directory'],
- archive_ready       => [1, 'Check the number of WAL files ready in the pg_xlog/archive_status'],
 };
 
 ## XXX Need to i18n the above
@@ -7489,6 +7489,26 @@ =head1 ACTIONS
 
 The current supported actions are:
 
+=head2 B<archive_ready>
+
+(C<symlink: check_postgres_archive_ready>) Checks how many WAL files with extension F<.ready> 
+exist in the F<pg_xlog/archive_status> directory, which is found 
+off of your B<data_directory>. This action must be run as a superuser, in order to access the 
+contents of the F<pg_xlog/archive_status> directory. The minimum version to use this action is 
+Postgres 8.1. The I<--warning> and I<--critical> options are simply the number of 
+F<.ready> files in the F<pg_xlog/archive_status> directory. 
+Usually, these values should be low, turning on the archive mechanism, we usually want it to 
+archive WAL files as fast as possible.
+
+If the archive command fail, number of WAL in your F<pg_xlog> directory will grow until
+exhausting all the disk space and force PostgreSQL to stop immediately.
+
+Example 1: Check that the number of ready WAL files is 10 or less on host "pluto"
+
+  check_postgres_archive_ready --host=pluto --critical=10
+
+For MRTG output, reports the number of ready WAL files on line 1.
+
 =head2 B<autovac_freeze>
 
 (C<symlink: check_postgres_autovac_freeze>) Checks how close each database is to the Postgres B<autovacuum_freeze_max_age> setting. This 
@@ -8537,26 +8557,6 @@ =head2 B<wal_files>
 
 For MRTG output, reports the number of WAL files on line 1.
 
-=head2 B<archive_ready>
-
-(C<symlink: check_postgres_archive_ready>) Checks how many WAL files with extension F<.ready> 
-exist in the F<pg_xlog/archive_status> directory, which is found 
-off of your B<data_directory>. This action must be run as a superuser, in order to access the 
-contents of the F<pg_xlog/archive_status> directory. The minimum version to use this action is 
-Postgres 8.1. The I<--warning> and I<--critical> options are simply the number of 
-F<.ready> files in the F<pg_xlog/archive_status> directory. 
-Usually, these values should be low, turning on the archive mechanism, we usually want it to 
-archive WAL files as fast as possible.
-
-If the archive command fail, number of WAL in your F<pg_xlog> directory will grow until
-exhausting all the disk space and force PostgreSQL to stop immediately.
-
-Example 1: Check that the number of ready WAL files is 10 or less on host "pluto"
-
-  check_postgres_archive_ready --host=pluto --critical=10
-
-For MRTG output, reports the number of ready WAL files on line 1.
-
 =head2 B<rebuild_symlinks>
 
 =head2 B<rebuild_symlinks_force>
