diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a38ef15a..04759a61 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -24,7 +24,7 @@ Code style
Code in repmgr should be formatted to the same standards as the main PostgreSQL
project. For more details see:
- https://www.postgresql.org/docs/current/static/source-format.html
+ https://www.postgresql.org/docs/current/source-format.html
Contributors should reformat their code similarly before submitting code to
the project, in order to minimize merge conflicts with other work.
diff --git a/configfile.c b/configfile.c
index 010e18a4..0a7afe5d 100644
--- a/configfile.c
+++ b/configfile.c
@@ -1524,7 +1524,7 @@ repmgr_atoi(const char *value, const char *config_item, ItemList *error_list, in
*
* TODO: accept "any unambiguous prefix of one of these" as per postgresql.conf:
*
- * https://www.postgresql.org/docs/current/static/config-setting.html
+ * https://www.postgresql.org/docs/current/config-setting.html
*/
bool
parse_bool(const char *s, const char *config_item, ItemList *error_list)
diff --git a/doc/appendix-faq.sgml b/doc/appendix-faq.sgml
index ba45ac98..e36b1b40 100644
--- a/doc/appendix-faq.sgml
+++ b/doc/appendix-faq.sgml
@@ -76,7 +76,7 @@
Before PostgreSQL 10, hash indexes were not WAL logged and are therefore not suitable
for use in streaming replication in PostgreSQL 9.6 and earlier. See the
- PostgreSQL documentation
+ PostgreSQL documentation
for details.
@@ -96,7 +96,7 @@
For major version upgrades (e.g. from PostgreSQL 9.6 to PostgreSQL 10),
the traditional approach is to "reseed" a cluster by upgrading a single
- node with pg_upgrade
+ node with pg_upgrade
and recloning standbys from this.
diff --git a/doc/appendix-release-notes.sgml b/doc/appendix-release-notes.sgml
index 680764e0..9b05830f 100644
--- a/doc/appendix-release-notes.sgml
+++ b/doc/appendix-release-notes.sgml
@@ -1332,7 +1332,7 @@
easier upgrades: &repmgr; is now implemented as a native
PostgreSQL extension, which means future upgrades can be carried out by
installing the upgraded package and issuing
- ALTER EXTENSION repmgr UPDATE.
+ ALTER EXTENSION repmgr UPDATE.
diff --git a/doc/cloning-standbys.sgml b/doc/cloning-standbys.sgml
index ab9dfe7b..22b60e70 100644
--- a/doc/cloning-standbys.sgml
+++ b/doc/cloning-standbys.sgml
@@ -262,7 +262,7 @@
meaning replication changes "cascade" down through a hierarchy of servers. This
can be used to reduce load on the primary and minimize bandwith usage between
sites. For more details, see the
-
+
PostgreSQL cascading replication documentation.
@@ -391,7 +391,7 @@
a symlink will automatically be created from the main data directory.
- See the PostgreSQL pg_basebackup documentation
+ See the PostgreSQL pg_basebackup documentation
for more details of available options.
@@ -413,7 +413,7 @@
user's ~/.pgpass file. It's also possible to store the password in the
environment variable PGPASSWORD, however this is not recommended for
security reasons. For more details see the
- PostgreSQL password file documentation.
+ PostgreSQL password file documentation.
diff --git a/doc/configuration-file-required-settings.sgml b/doc/configuration-file-required-settings.sgml
index 51cce424..5a72447a 100644
--- a/doc/configuration-file-required-settings.sgml
+++ b/doc/configuration-file-required-settings.sgml
@@ -56,7 +56,7 @@
For details on conninfo strings, see section Connection Strings
+ url="https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING">Connection Strings
in the PosgreSQL documentation.
@@ -64,7 +64,7 @@
connect_timeout in the conninfo
string to determine the length of time which elapses before a network
connection attempt is abandoned; for details see
+ url="https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-CONNECT-TIMEOUT">
the PostgreSQL documentation.
diff --git a/doc/install-source.sgml b/doc/install-source.sgml
index e2a0c8a5..3e9e76e4 100644
--- a/doc/install-source.sgml
+++ b/doc/install-source.sgml
@@ -12,8 +12,8 @@
To install &repmgr; the prerequisites for compiling
&postgres; must be installed. These are described in &postgres;'s
documentation
- on build requirements
- and build requirements for documentation.
+ on build requirements
+ and build requirements for documentation.
@@ -146,7 +146,7 @@
The &repmgr; documentation is (like the main PostgreSQL project)
written in DocBook format. To build it locally as HTML, you'll need to
install the required packages as described in the
-
+
PostgreSQL documentation then execute:
./configure && make install-doc
diff --git a/doc/quickstart.sgml b/doc/quickstart.sgml
index bd6a3ebd..c6c0fee8 100644
--- a/doc/quickstart.sgml
+++ b/doc/quickstart.sgml
@@ -90,7 +90,7 @@
# PostgreSQL 9.6 and later: one of 'replica' or 'logical'
# ('hot_standby' will still be accepted as an alias for 'replica')
#
- # See: https://www.postgresql.org/docs/current/static/runtime-config-wal.html#GUC-WAL-LEVEL
+ # See: https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-WAL-LEVEL
wal_level = 'hot_standby'
@@ -215,7 +215,7 @@
&repmgr; stores connection information as libpq
+ url="https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING">libpq
connection strings throughout. This documentation refers to them as conninfo
strings; an alternative name is DSN (data source name).
We'll use these in place of the -h hostname -d databasename -U username syntax.
@@ -437,7 +437,7 @@
From PostgreSQL 9.6 you can also use the view
-
+
pg_stat_wal_receiver to check the replication status from the standby.
diff --git a/doc/repmgr-node-rejoin.sgml b/doc/repmgr-node-rejoin.sgml
index c32285aa..c906bd2e 100644
--- a/doc/repmgr-node-rejoin.sgml
+++ b/doc/repmgr-node-rejoin.sgml
@@ -188,7 +188,7 @@
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.
+ pg_rewind documentation for details.
diff --git a/doc/repmgr-standby-clone.sgml b/doc/repmgr-standby-clone.sgml
index ef0728f8..f1c2c634 100644
--- a/doc/repmgr-standby-clone.sgml
+++ b/doc/repmgr-standby-clone.sgml
@@ -170,7 +170,7 @@
pg_basebackup_options='--xlog-method=fetch'
and ensure that wal_keep_segments is set to an appropriately high value.
- See the
+ See the
pg_basebackup documentation for details.
diff --git a/doc/repmgrd-configuration.sgml b/doc/repmgrd-configuration.sgml
index cc5c2722..34035d8a 100644
--- a/doc/repmgrd-configuration.sgml
+++ b/doc/repmgrd-configuration.sgml
@@ -31,7 +31,7 @@
Changing this setting requires a restart of PostgreSQL; for more details see
- the PostgreSQL documentation.
+ the PostgreSQL documentation.
@@ -512,7 +512,7 @@ REPMGRD_OPTS="--daemonize=false"
For further details on conninfo network connection
parameters, see the
- PostgreSQL documentation.
+ PostgreSQL documentation.
diff --git a/doc/switchover.sgml b/doc/switchover.sgml
index 754932c2..758a6cb9 100644
--- a/doc/switchover.sgml
+++ b/doc/switchover.sgml
@@ -236,7 +236,7 @@
For more details on pg_rewind, see:
- https://www.postgresql.org/docs/current/static/app-pgrewind.html.
+ https://www.postgresql.org/docs/current/app-pgrewind.html.
pg_rewind has been part of the core PostgreSQL distribution since
@@ -347,7 +347,7 @@
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
+ pg_rewind documentation
for details.
@@ -418,7 +418,7 @@ HINT: stop backup before attempting the switchover
To proceed, either wait until the backup has finished, or cancel it with the command
SELECT pg_stop_backup(). For more details see the PostgreSQL
documentation section
- Making an exclusive low level backup.
+ Making an exclusive low level backup.
diff --git a/doc/upgrading-repmgr.sgml b/doc/upgrading-repmgr.sgml
index 36c567a5..d9086e77 100644
--- a/doc/upgrading-repmgr.sgml
+++ b/doc/upgrading-repmgr.sgml
@@ -247,7 +247,7 @@ ALTER EXTENSION repmgr UPDATE
- For further details please see the pg_upgrade documentation.
+ For further details please see the pg_upgrade documentation.
If replication slots are in use, bear in mind these will not
diff --git a/repmgr.conf.sample b/repmgr.conf.sample
index 32c326ab..1d758057 100644
--- a/repmgr.conf.sample
+++ b/repmgr.conf.sample
@@ -27,13 +27,13 @@
# the local node using this string.
#
# For details on conninfo strings, see:
- # https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNSTRING
+ # https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING
#
# If repmgrd is in use, consider explicitly setting
# "connect_timeout" in the conninfo string to determine
# the length of time which elapses before a network
# connection attempt is abandoned; for details see:
- # https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNECT-CONNECT-TIMEOUT
+ # https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-CONNECT-TIMEOUT
#data_directory='' # The node's data directory. This is needed by repmgr
# when performing operations when the PostgreSQL instance