Update links in docs to https where possible, and fix a couple of broken/out of date ones.

docs/en_US/add_restore_point_dialog.rst

@@ -19,7 +19,7 @@ the restore point to add* to provide a descriptive name for the restore point.
 
 For more information about using a restore point as a recovery target, please
 see the
-`PostgreSQL documentation <http://www.postgresql.org/docs/9.5/static/recovery-target-settings.html#RECOVERY-TARGET-NAME>`_.
+`PostgreSQL documentation <https://www.postgresql.org/docs/current/recovery-target-settings.html#RECOVERY-TARGET-NAME>`_.
 
 * Click the *OK* button to save the restore point.
 * Click the *Cancel* button to exit without saving work.

docs/en_US/build_code_snippet.py

@@ -72,7 +72,7 @@ print_code(
         """
 NodeView class helps exposing basic REST APIs for different operations used by
 pgAdmin Browser. The basic idea has been taken from the `Flask's MethodView
-<http://flask.pocoo.org/docs/0.10/api/#flask.views.MethodView>`_ class. Because
+<http://flask.pocoo.org/docs/1.0/api/#flask.views.MethodView>`_ class. Because
 - we need a lot more operations (not, just CRUD), we can not use it directly.""")
 
 from pgadmin.utils.driver.abstract import BaseDriver, BaseConnection

docs/en_US/collation_dialog.rst

@@ -76,7 +76,7 @@ rules specified for the locale, *fr-BI-x-icu.  The collation is owned by
   setting a locale, see Chapter 22.1 Locale Support of the PostgreSQL core
   documentation:
 
-   http://www.postgresql.org/docs/current/static/locale.html
+   https://www.postgresql.org/docs/current/locale.html
 
 * Click the *Save* button to save work.
 * Click the *Cancel* button to exit without saving work.

docs/en_US/column_dialog.rst

@@ -61,7 +61,7 @@ command. Click the *Add* icon (+) to add a *Name*/*Value* pair:
 
 * Specify the number of distinct values in the *Value* field. For more
   information, see the documentation for
-  `ALTER TABLE  <http://www.postgresql.org/docs/9.6/static/sql_altertable.html>`_.
+  `ALTER TABLE  <https://www.postgresql.org/docs/current/sql-altertable.html>`_.
 
 Click the *Add* icon (+) to specify each additional *Name*/*Value* pair; to
 discard a variable, click the trash icon to the left of the row and confirm

docs/en_US/connect_error.rst

@@ -37,7 +37,7 @@ can be done by adding **listen_addresses='*'**; this will make the server accept
 connections on any IP interface.
 
 For further information, please refer to the PostgreSQL documentation about
-`runtime configuration <http://www.postgresql.org/docs/current/interactive/runtime-config.html>`_.
+`runtime configuration <https://www.postgresql.org/docs/current/runtime-config.html>`_.
 
 **FATAL: no pg_hba.conf entry**
 
@@ -57,7 +57,7 @@ the pg_hba.conf file on the database server host, and add an entry in the form:
  * **host template1 postgres ::ffff:192.168.0.0/120 md5** for an IPV6 network
 
 For more information, please refer to the PostgreSQL documentation about
-`client authentication <http://www.postgresql.org/docs/current/interactive/client-authentication.html>`_.
+`client authentication <https://www.postgresql.org/docs/current/client-authentication.html>`_.
 
 **FATAL: password authentication failed**
 

docs/en_US/function_dialog.rst

@@ -76,7 +76,7 @@ function:
   replacing an existing function definition. For more information about the
   CREATE FUNCTION command, see the PostgreSQL core documentation available at:
 
-   http://www.postgresql.org/docs/current/static/functions-window.html
+   https://www.postgresql.org/docs/current/functions-window.html
 
 * Use the *Estimated cost* field to specify a positive number representing the
   estimated execution cost for the function, in units of cpu_operator_cost. If

docs/en_US/grant_wizard.rst

@@ -62,7 +62,7 @@ the object.
   deletion in the *Delete Row* dialog.
 
 For more information about granting privileges on database objects, see the
-`PostgreSQL core documentation <http://www.postgresql.org/docs/current/static/sql-grant.html>`_.
+`PostgreSQL core documentation <https://www.postgresql.org/docs/current/sql-grant.html>`_.
 
 Click the *Next* button to continue, the *Back* button to select or deselect
 additional database objects, or the *Cancel* button to close the wizard without

docs/en_US/licence.rst

@@ -5,7 +5,7 @@
 ****************
 
 pgAdmin is released under the
-`PostgreSQL Licence <http://www.postgresql.org/about/licence>`_, which is a
+`PostgreSQL Licence <https://www.postgresql.org/about/licence>`_, which is a
 liberal Open Source licence similar to BSD or MIT, and approved by the Open
 Source Initiative. The copyright for the project source code, website and
 documentation is attributed to the

docs/en_US/pgagent_install.rst

@@ -82,7 +82,7 @@ needed for debugging or specialised configurations::
     -l <logging verbosity (ERROR=0, WARNING=1, DEBUG=2, default 0)>
 
 The connection string is a standard PostgreSQL libpq connection string (see
-the `PostgreSQL documentation on the connection string <http://www.postgresql.org/docs/current/static/libpq.html#libpq-connect>`_
+the `PostgreSQL documentation on the connection string <https://www.postgresql.org/docs/current/libpq.html#libpq-connect>`_
 for further details). For example, the following command line will run pgAgent
 against a server listening on the localhost, using a database called 'pgadmin',
 connecting as the user 'postgres':

docs/en_US/pgagent_jobs.rst

@@ -78,7 +78,7 @@ Use fields on the step definition dialog to define the step:
 * Use the *Connection string* field to specify a libpq-style connection string
   to the remote server on which the step will be performed. For more information
   about writing a connection string, please see the
-  `PostgreSQL documentation <http://www.postgresql.org/docs/current/static/libpq.html#libpq-connect>`_.
+  `PostgreSQL documentation <https://www.postgresql.org/docs/current/libpq.html#libpq-connect>`_.
 * Use the *On error* drop-down to specify the behavior of pgAgent if it
   encounters an error while executing the step.  Select from:
 

docs/en_US/restore_dialog.rst

@@ -12,8 +12,8 @@ utility; the *Restore* dialog invokes options of the pg_restore client utility.
 You can use the *Query Tool* to play back the script created during a plain-text
 backup made with the *Backup* dialog.  For more information about backing up or
 restoring, please refer to the documentation for
-`pg_dump <https://www.postgresql.org/docs/9.5/static/app-pgdump.html>`_ or
+`pg_dump <https://www.postgresql.org/docs/current/app-pgdump.html>`_ or
-`pg_restore <https://www.postgresql.org/docs/9.5/static/app-pgrestore.html>`_.
+`pg_restore <https://www.postgresql.org/docs/current/app-pgrestore.html>`_.
 
 .. image:: images/restore_general.png
     :alt: Restore dialog general tab

docs/en_US/server_dialog.rst

@@ -59,7 +59,7 @@ Use the fields in the *Connection* tab to configure a connection:
   connecting role must be a member of the role specified.
 * Use the *Service* field to specify the service name. For more information,
   see
-  `Section 33.16 of the Postgres documentation <https://www.postgresql.org/docs/10/static/libpq-pgservice.html>`_.
+  `Section 33.16 of the Postgres documentation <https://www.postgresql.org/docs/current/libpq-pgservice.html>`_.
 
 Click the *SSL* tab to continue.
 
@@ -72,7 +72,7 @@ Use the fields in the *SSL* tab to configure SSL:
 * Use the drop-down list box in the *SSL* field to select the type of SSL
   connection the server should use. For more information about using SSL
   encryption, see
-  `Section 33.18 of the Postgres documentation <https://www.postgresql.org/docs/current/static/libpq-ssl.html>`_.
+  `Section 33.18 of the Postgres documentation <https://www.postgresql.org/docs/current/libpq-ssl.html>`_.
 
 If pgAdmin is installed in Server mode (the default mode), you can use the
 platform-specific File manager dialog to upload files that support SSL
@@ -167,7 +167,7 @@ Use the fields in the *Advanced* tab to configure a connection:
 * Use the *Password File* field to specify the location of a password file
   (.pgpass). A .pgpass file allows a user to login without providing a password
   when they connect.  For more information, see
-  `Section 33.15 of the Postgres documentation <http://www.postgresql.org/docs/current/static/libpq-pgpass.html>`_.
+  `Section 33.15 of the Postgres documentation <https://www.postgresql.org/docs/current/libpq-pgpass.html>`_.
 * Use the *Connection timeout* field to specify the maximum wait for connection,
   in seconds. Zero or not specified means wait indefinitely. It is not
   recommended to use a timeout of less than 2 seconds.

docs/en_US/using_pgagent.rst

@@ -39,7 +39,7 @@ connection string - on Unix systems it may be visible to all users in *ps*
 output, and on Windows systems it will be stored in the registry in plain text.
 Instead, use a libpq *~/.pgpass* file to store the passwords for every database
 that pgAgent must access. Details of this technique may be found in the
-`PostgreSQL documentation on .pgpass file <http://www.postgresql.org/docs/current/static/libpq-pgpass.html>`_.
+`PostgreSQL documentation on .pgpass file <https://www.postgresql.org/docs/current/libpq-pgpass.html>`_.
 
 **System/database access** - all jobs run by pgAgent will run with the security
 privileges of the pgAgent user. SQL steps will run as the user that pgAgent