summaryrefslogtreecommitdiff
path: root/check_postgres.pl
diff options
context:
space:
mode:
authorGreg Sabino Mullane2009-04-22 20:22:26 +0000
committerGreg Sabino Mullane2009-04-22 20:22:26 +0000
commit8f86fc8f9f057d65ce9a54845179f8b850a52ba1 (patch)
treee04ea557b738be4641e04086cbc8829b74c874a9 /check_postgres.pl
parente5b7024ffc46429d53dd5eaef2ba201c9049a115 (diff)
Wording change for new prepare_txns action.
Diffstat (limited to 'check_postgres.pl')
-rwxr-xr-xcheck_postgres.pl7
1 files changed, 4 insertions, 3 deletions
diff --git a/check_postgres.pl b/check_postgres.pl
index e312effbc..85068a05a 100755
--- a/check_postgres.pl
+++ b/check_postgres.pl
@@ -5499,9 +5499,10 @@ It is recommended this check is run at least once a day.
(C<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
-and complicated to maintain. Thus, the default value for a warning is 1 second, to detect any
-use of prepared transactions, which is probably a mistake on most systems. Warning and critical
-as the number of seconds a prepared transaction has been open before an alert is given.
+and complicated to maintain. They should also not be confused with prepared STATEMENTS, which is
+what most people think of when they hear prepare. The default value for a warning is 1 second, to
+detect any use of prepared transactions, which is probably a mistake on most systems. Warning and
+critical are the number of seconds a prepared transaction has been open before an alert is given.
Example 1: Give a warning on detecting any prepared transactions: