From 9f95e492ee3972943231de6f420762790c8253fe Mon Sep 17 00:00:00 2001 From: Magnus Hagander Date: Wed, 25 May 2016 11:44:37 +0200 Subject: Update URLs to www.postgresql.org to be https The main PostgreSQL website is now https only. The versions.rss check still works by following the redirect, but it's more efficient to hit the https URL directly. In passing, also update all the direct links in the documentation to be https. --- check_postgres.pl.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'check_postgres.pl.html') diff --git a/check_postgres.pl.html b/check_postgres.pl.html index 6122ea33c..09304672f 100644 --- a/check_postgres.pl.html +++ b/check_postgres.pl.html @@ -230,7 +230,7 @@
This file contains a simple list of connection options. You can also pass additional information when using this option such as --dbservice="maindatabase sslmode=require"
-The documentation for this file can be found at http://www.postgresql.org/docs/current/static/libpq-pgservice.html
+The documentation for this file can be found at https://www.postgresql.org/docs/current/static/libpq-pgservice.html
@@ -1285,7 +1285,7 @@(symlink: check_postgres_txn_wraparound
) Checks how close to transaction wraparound one or more databases are getting. The --warning and --critical options indicate the number of transactions done, and must be a positive integer. If either option is not given, the default values of 1.3 and 1.4 billion are used. There is no need to run this command more than once per database cluster. For a more detailed discussion of what this number represents and what to do about it, please visit the page http://www.postgresql.org/docs/current/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND
(symlink: check_postgres_txn_wraparound
) Checks how close to transaction wraparound one or more databases are getting. The --warning and --critical options indicate the number of transactions done, and must be a positive integer. If either option is not given, the default values of 1.3 and 1.4 billion are used. There is no need to run this command more than once per database cluster. For a more detailed discussion of what this number represents and what to do about it, please visit the page https://www.postgresql.org/docs/current/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND
The warning and critical values can have underscores in the number for legibility, as Perl does.
-- cgit v1.2.3