From bd76d0eb92c22bfd8295d1a2ab0fdeb1031f4ba6 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Mon, 27 Jun 2016 12:32:10 +0900 Subject: [PATCH] Update postgresql.org links to https --- FAQ.md | 2 +- README.md | 10 +++++----- repmgr.conf.sample | 4 +++- 3 files changed, 9 insertions(+), 7 deletions(-) diff --git a/FAQ.md b/FAQ.md index 0ecca1e9..2abbfdce 100644 --- a/FAQ.md +++ b/FAQ.md @@ -38,7 +38,7 @@ General No. Hash indexes and replication do not mix well and their use is explicitly discouraged; see: - http://www.postgresql.org/docs/current/interactive/sql-createindex.html#AEN74175 + https://www.postgresql.org/docs/current/interactive/sql-createindex.html#AEN74175 `repmgr` -------- diff --git a/README.md b/README.md index 7366782a..9f2bb979 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,7 @@ This guide assumes that you are familiar with PostgreSQL administration and streaming replication concepts. For further details on streaming replication, see this link: - http://www.postgresql.org/docs/current/interactive/warm-standby.html#STREAMING-REPLICATION + https://www.postgresql.org/docs/current/interactive/warm-standby.html#STREAMING-REPLICATION The following terms are used throughout the `repmgr` documentation. @@ -472,7 +472,7 @@ so should be used with care. Further options can be passed to the `pg_basebackup` utility via the setting `pg_basebackup_options` in `repmgr.conf`. See the PostgreSQL documentation for more details of available options: - http://www.postgresql.org/docs/current/static/app-pgbasebackup.html + https://www.postgresql.org/docs/current/static/app-pgbasebackup.html ### Using rsync to clone a standby @@ -608,13 +608,13 @@ place. If using the default `pg_basebackup` method, we recommend setting pg_basebackup_options='--xlog-method=stream' See the `pg_basebackup` documentation for details: - http://www.postgresql.org/docs/current/static/app-pgbasebackup.html + https://www.postgresql.org/docs/current/static/app-pgbasebackup.html Otherwise it's necessary to set `wal_keep_segments` to an appropriately high value. Further information on replication slots in the PostgreSQL documentation: - http://www.postgresql.org/docs/current/interactive/warm-standby.html#STREAMING-REPLICATION-SLOTS + https://www.postgresql.org/docs/current/interactive/warm-standby.html#STREAMING-REPLICATION-SLOTS Promoting a standby server with repmgr @@ -816,7 +816,7 @@ should have been updated to reflect this: - `pg_rewind` *requires* that either `wal_log_hints` is enabled, or that data checksums were enabled when the cluster was initialized. See the `pg_rewind` documentation for details: - http://www.postgresql.org/docs/current/static/app-pgrewind.html + https://www.postgresql.org/docs/current/static/app-pgrewind.html - `repmgrd` should not be running when a switchover is carried out, otherwise the `repmgrd` may try and promote a standby by itself. - Any other standbys attached to the old master will need to be manually diff --git a/repmgr.conf.sample b/repmgr.conf.sample index 4cfa3d71..aeab45c8 100644 --- a/repmgr.conf.sample +++ b/repmgr.conf.sample @@ -28,7 +28,9 @@ # Database connection information as a conninfo string # This must be accessible to all servers in the cluster; for details see: -# http://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNSTRING +# +# https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNSTRING +# #conninfo='host=192.168.204.104 dbname=repmgr_db user=repmgr_usr' # Optional configuration items