From d699570317b8ea098ab1697ad9c33edb7001b941 Mon Sep 17 00:00:00 2001 From: Greg Sabino Mullane Date: Wed, 7 Apr 2010 11:36:02 -0400 Subject: [PATCH] Clarify checkpoint docs. --- check_postgres.pl | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/check_postgres.pl b/check_postgres.pl index faec760df..1ba74f096 100755 --- a/check_postgres.pl +++ b/check_postgres.pl @@ -7166,10 +7166,10 @@ times larger the relation is compared to how large it should be), just pass in C =head2 B (C) 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 C, 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 C, or passing the C<--datadir> argument. It returns the number of seconds since the last checkpoint was run, as determined by parsing the call to C. Because of this, the pg_controldata executable must be available in the current path. Alternatively, you can -- 2.39.5