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.

diff --git a/check_postgres.pl b/check_postgres.pl
index 8f63b85efddaf75a100bcca47b7283b24697dc44..178fb3763011da921629c42d620075b201d59ff7 100755 (executable)
--- a/check_postgres.pl
+++ b/check_postgres.pl
@@ -5767,7 +5767,7 @@ sub check_new_version_pg {
 
     ## Check if a new version of Postgres is available
 
-    my $url = 'http://www.postgresql.org/versions.rss';
+    my $url = 'https://www.postgresql.org/versions.rss';
 
     ## Grab the local version
     my $info = run_command('SELECT version() AS version');
@@ -8064,7 +8064,7 @@ sub check_txn_wraparound {
     ## Supports: Nagios, MRTG
     ## Warning and critical are the number of transactions performed
     ## Thus, anything *over* that number will trip the alert
-    ## See: http://www.postgresql.org/docs/current/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND
+    ## See: https://www.postgresql.org/docs/current/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND
     ## It makes no sense to run this more than once on the same cluster
 
     my ($warning, $critical) = validate_range
@@ -8392,7 +8392,7 @@ This file contains a simple list of connection options. You can also pass additi
 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
+https://www.postgresql.org/docs/current/static/libpq-pgservice.html
 
 =back
 
@@ -9858,7 +9858,7 @@ The I<--warning> and I<--critical> options indicate the number of transactions d
 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 
-L<http://www.postgresql.org/docs/current/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND>
+L<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.
 

diff --git a/check_postgres.pl.html b/check_postgres.pl.html
index 6122ea33cc5742e26cdb59e4b961496c7f3e70a4..09304672fe9d4254622544f38a74faa3954bf5a5 100644 (file)
--- a/check_postgres.pl.html
+++ b/check_postgres.pl.html
@@ -230,7 +230,7 @@
 
 <p>This file contains a simple list of connection options. You can also pass additional information when using this option such as --dbservice=&quot;maindatabase sslmode=require&quot;</p>
 
-<p>The documentation for this file can be found at http://www.postgresql.org/docs/current/static/libpq-pgservice.html</p>
+<p>The documentation for this file can be found at https://www.postgresql.org/docs/current/static/libpq-pgservice.html</p>
 
 </dd>
 </dl>
@@ -1285,7 +1285,7 @@
 
 <h2 id="txn_wraparound"><b>txn_wraparound</b></h2>
 
-<p>(<code>symlink: check_postgres_txn_wraparound</code>) Checks how close to transaction wraparound one or more databases are getting. The <i>--warning</i> and <i>--critical</i> 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 <a href="http://www.postgresql.org/docs/current/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND">http://www.postgresql.org/docs/current/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND</a></p>
+<p>(<code>symlink: check_postgres_txn_wraparound</code>) Checks how close to transaction wraparound one or more databases are getting. The <i>--warning</i> and <i>--critical</i> 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 <a href="https://www.postgresql.org/docs/current/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND">https://www.postgresql.org/docs/current/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND</a></p>
 
 <p>The warning and critical values can have underscores in the number for legibility, as Perl does.</p>