Update HISTORY

.github/CODEOWNERS

@@ -1,7 +0,0 @@
-# Each line is a file pattern followed by one or more owners.
-
-# These owners will be the default owners for everything in
-# the repo. Unless a later match takes precedence,
-# @global-owner1 and @global-owner2 will be requested for
-# review when someone opens a pull request.
-*       @EnterpriseDB/repmgr-dev

.gitignore

@@ -39,20 +39,12 @@ lib*.pc
 
 # test output
 /results/
-/regression.diffs
-/regression.out
 
 # other
 /.lineno
 *.dSYM
-*.orig
-*.rej
-
 # generated binaries
 repmgr
 repmgrd
 repmgr4
 repmgrd4
-
-# generated files
-configfile-scan.c

CONTRIBUTING.md

@@ -2,7 +2,7 @@ License and Contributions
 =========================
 
 `repmgr` is licensed under the GPL v3.  All of its code and documentation is
-Copyright 2010-2021, EnterpriseDB Corporation.  See the files COPYRIGHT and LICENSE for
+Copyright 2010-2017, 2ndQuadrant Limited.  See the files COPYRIGHT and LICENSE for
 details.
 
 The development of repmgr has primarily been sponsored by 2ndQuadrant customers.
@@ -12,10 +12,10 @@ which has received funding from the European Union's Seventh Framework Programme
 (FP7/2007-2013) under grant agreement 258862.
 
 Contributions to `repmgr` are welcome, and will be listed in the file `CREDITS`.
-EnterpriseDB Corporation requires that any contributions provide a copyright
+2ndQuadrant Limited requires that any contributions provide a copyright
 assignment and a disclaimer of any work-for-hire ownership claims from the
 employer of the developer.  This lets us make sure that all of the repmgr
-distribution remains free code.  Please contact info@enterprise.com for a
+distribution remains free code.  Please contact info@2ndQuadrant.com for a
 copy of the relevant Copyright Assignment Form.
 
 Code style
@@ -24,7 +24,8 @@ 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/source-format.html
+    https://www.postgresql.org/docs/current/static/source-format.html
 
 Contributors should reformat their code similarly before submitting code to
 the project, in order to minimize merge conflicts with other work.
+>>>>>>> Add further documentation files

COPYRIGHT

@@ -1,4 +1,4 @@
-Copyright (c) 2010-2021, EnterpriseDB Corporation
+Copyright (c) 2010-2017, 2ndQuadrant Limited
 All rights reserved.
 
 This program is free software: you can redistribute it and/or modify
@@ -12,5 +12,5 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
-along with this program.  If not, see https://www.gnu.org/licenses/
+along with this program.  If not, see http://www.gnu.org/licenses/
 to obtain one.

FAQ.md

@@ -1,10 +0,0 @@
-FAQ - Frequently Asked Questions about repmgr
-=============================================
-
-The repmgr 4 FAQ is located here: [repmgr FAQ (Frequently Asked Questions)](https://repmgr.org/docs/current/appendix-faq.html "repmgr FAQ")
-
-The repmgr 3.x FAQ can be found here:
-
-    https://github.com/EnterpriseDB/repmgr/blob/REL3_3_STABLE/FAQ.md
-
-Note that repmgr 3.x is no longer supported.

HISTORY

@@ -1,344 +1,6 @@
-5.5.0   2024-11-20
+4.0     2017-10-04
-        Support for PostgreSQL 17 added
+        Complete rewrite with many changes; see file "doc/upgrading-from-repmgr3.md"
-        Fix warnings detected by the -Wshadow=compatible-local
+        for details.
-          added in PostgreSQL 16
-
-5.4.1   2023-07-04
-        repmgrd: ensure witness node metadata is updated (Ian)
-
-5.4.0   2023-03-16
-        Support cloning replicas using pg-backup-api
-
-5.3.3   2022-10-17
-        Support for PostgreSQL added
-        repmgrd: ensure event notification script is called for event
-          "repmgrd_upstream_disconnect"; GitHub #760 (Ian)
-
-5.3.2   2022-05-25
-        standby clone: don't error out if unable to determine cluster size (Ian)
-        node check: fix --downstream --nagios output; GitHub #749 (Ian)
-        repmgrd: ensure witness node marked active (hslightdb)
-        repmgrd: improve walsender disable check (Ian)
-        general: ensure replication slots can be dropped by a
-          replication-only user (Ian)
-
-5.3.1   2022-02-15
-        repmgrd: fixes for potential connection leaks (hslightdb)
-        repmgr: fix upgrade path from repmgr 4.2 and 4.3 to repmgr 5.3 (Ian)
-
-5.3.0   2021-10-12
-        standby switchover: improve handling of node rejoin failure (Ian)
-        repmgrd: prefix all shared library functions with "repmgr_" to
-          minimize the risk of clashes with other shared libraries (Ian)
-        repmgrd: at startup, if node record is marked as "inactive", attempt
-          to set it to "active" (Ian)
-        standby clone: set "slot_name" in node record if required (Ian)
-        node rejoin: emit rejoin target note information as NOTICE (Ian)
-        repmgrd: ensure short option "-s" is accepted (Ian)
-
-5.2.1   2020-12-07
-        config: fix parsing of "replication_type"; GitHub #672 (Ian)
-        standby clone: handle missing "postgresql.auto.conf" (Ian)
-        standby clone: add option --recovery-min-apply-delay (Ian)
-        standby clone: fix data directory permissions handling for
-          PostgreSQL 11 and later (Ian)
-        repmgrd: prevent termination when local node not available and
-          standby_disconnect_on_failover; GitHub #675 (Ian)
-        repmgrd: ensure reconnect_interval" is correctly handled;
-          GitHub #673 (Ian)
-
-5.2.0   2020-10-22
-        general: add support for PostgreSQL 13 (Ian)
-        general: remove support for PostgreSQL 9.3 (Ian)
-        config: add support for file inclusion directives (Ian)
-        repmgr: "primary unregister --force" will unregister an active primary
-          with no registered standby nodes (Ian)
-        repmgr: add option --verify-backup to "standby clone" (Ian)
-        repmgr: "standby clone" honours --waldir option if set in
-          "pg_basebackup_options" (Ian)
-        repmgr: add option --db-connection to "node check" (Ian)
-        repmgr: report database connection error if the --optformat option was
-          provided to "node check" (Ian)
-        repmgr: improve "node rejoin" checks (Ian)
-        repmgr: enable "node rejoin" to join a target with a lower timeline (Ian)
-        repmgr: support pg_rewind's automatic crash recovery in Pg13 and later (Ian)
-        repmgr: improve output formatting for cluster matrix/crosscheck (Ian)
-        repmgr: improve database connection failure error checking on the
-          demotion candidate during "standby switchover" (Ian)
-        repmgr: make repmgr metadata tables dumpable (Ian)
-        repmgr: fix issue with tablespace mapping when cloning from Barman;
-          GitHub #650 (Ian)
-        repmgr: improve handling of pg_control read errors (Ian)
-        repmgrd: add additional optional parameters to "failover_validation command"
-          (spaskalev; GitHub #651)
-        repmgrd: ensure primary connection is reset if same as upstream;
-          GitHub #633 (Ian)
-
-5.1.0   2020-04-13
-        repmgr: remove BDR 2.x support
-        repmgr: don't query upstream's data directory (Ian)
-        repmgr: rename --recovery-conf-only to --replication-conf-only (Ian)
-        repmgr: ensure postgresql.auto.conf is created with correct permissions (Ian)
-        repmgr: minimize requirement to check upstream data directory location
-          during "standby clone" (Ian)
-        repmgr: warn about missing pg_rewind prerequisites when executing
-          "standby clone" (Ian)
-        repmgr: add --upstream option to "node check"
-        repmgr: report error code on follow/rejoin failure due to non-available
-          replication slot (Ian)
-        repmgr: ensure "node rejoin" checks for available replication slots (Ian)
-        repmgr: improve "standby switchover" completion checks (Ian)
-        repmgr: add replication configuration file ownership check to
-          "standby switchover" (Ian)
-        repmgr: check the demotion candidate's registered repmgr.conf file can
-          be found (laixiong; GitHub 615)
-        repmgr: consolidate replication connection code (Ian)
-        repmgr: check permissions for "pg_promote()" and fall back to pg_ctl
-          if necessary (Ian)
-        repmgr: in --dry-run mode, display promote command which will be used (Ian)
-        repmgr: enable "service_promote_command" in PostgreSQL 12 (Ian)
-        repmgr: accept option -S/--superuser for "node check"; GitHub #612 (Ian)
-
-5.0     2019-10-15
-        general: add PostgreSQL 12 support (Ian)
-        general: parse configuration file using flex (Ian)
-        repmgr: rename "repmgr daemon ..." commands to "repmgr service ..." (Ian)
-        repmgr: improve data directory check (Ian)
-        repmgr: improve extension check during "standby clone" (Ian)
-		repmgr: pass provided log level when executing repmgr remotely (Ian)
-        repmgrd: fix handling of upstream node change check (Ian)
-
-4.4     2019-06-27
-        repmgr: improve "daemon status" output (Ian)
-        repmgr: add "--siblings-follow" option to "standby promote" (Ian)
-        repmgr: add "--repmgrd-force-unpause" option to "standby switchover" (Ian)
-        repmgr: fix data directory permissions issue in barman mode where
-          an existing directory is being overwritten (Ian)
-        repmgr: improve "--dry-run" behaviour for "standby promote" and
-          "standby switchover" (Ian)
-        repmgr: when running "standby clone" with the "--upstream-conninfo" option
-          ensure that "application_name" is set correctly in "primary_conninfo" (Ian)
-        repmgr: ensure "--dry-run" together with --force when running "standby clone"
-          in barman mode does not modify an existing data directory (Ian)
-        repmgr: improve "--dry-run" output when running "standby clone" in
-          basebackup mode (Ian)
-        repmgr: improve upstream walsender checks when running "standby clone" (Ian)
-        repmgr: display node timeline ID in "cluster show" output (Ian)
-        repmgr: in "cluster show" and "daemon status", show upstream node name
-          as reported by each individual node (Ian)
-        repmgr: in "cluster show" and "daemon status", check if a node is attached
-          to its advertised upstream node
-        repmgr: use --compact rather than --terse option in "cluster event" (Ian)
-        repmgr: prevent a standby being cloned from a witness server (Ian)
-        repmgr: prevent a witness server being registered on the cluster primary (John)
-        repmgr: ensure BDR2-specific functionality cannot be used on
-          BDR3 and later (Ian)
-        repmgr: canonicalize the data directory path (Ian)
-        repmgr: note that "standby follow" requires a primary to be available (Ian)
-        repmgrd: monitor standbys attached to primary (Ian)
-        repmgrd: add "primary visibility consensus" functionality (Ian)
-        repmgrd: fix memory leak which occurs while the monitored PostgreSQL
-           node is not running (Ian)
-        general: documentation converted to DocBook XML format (Ian)
-
-4.3     2019-04-02
-        repmgr: add "daemon (start|stop)" command; GitHub #528 (Ian)
-        repmgr: add --version-number command line option (Ian)
-        repmgr: add --compact option to "cluster show"; GitHub #521 (Ian)
-        repmgr: cluster show - differentiate between unreachable nodes
-          and nodes which are running but rejecting connections (Ian)
-        repmgr: add --dry-run option to "standby promote"; GitHub #522 (Ian)
-        repmgr: add "node check --data-directory-config"; GitHub #523 (Ian)
-        repmgr: prevent potential race condition in "standby switchover"
-          when checking received WAL location; GitHub #518 (Ian)
-        repmgr: ensure "standby switchover" verifies repmgr can read the
-          data directory on the demotion candidate; GitHub #523 (Ian)
-        repmgr: ensure "standby switchover" verifies replication connection
-          exists; GitHub #519 (Ian)
-        repmgr: add sanity check for correct extension version (Ian)
-        repmgr: ensure "witness register --dry-run" does not attempt to read node
-          tables if repmgr extension not installed; GitHub #513 (Ian)
-        repmgr: ensure "standby register" fails when --upstream-node-id is the
-          same as the local node ID (Ian)
-        repmgrd: check binary and extension major versions match; GitHub #515 (Ian)
-        repmgrd: on a cascaded standby, don't fail over if "failover=manual";
-          GitHub #531 (Ian)
-        repmgrd: don't consider nodes where repmgrd is not running as promotion
-          candidates (Ian)
-        repmgrd: add option "connection_check_type" (Ian)
-        repmgrd: improve witness monitoring when primary node not available (Ian)
-		repmgrd: handle situation where a primary has unexpectedly appeared
-		  during failover; GitHub #420 (Ian)
-		general: fix Makefile (John)
-
-4.2     2018-10-24
-        repmgr: add parameter "shutdown_check_timeout" for use by "standby switchover";
-          GitHub #504 (Ian)
-        repmgr: add "--node-id" option to "repmgr cluster cleanup"; GitHub #493 (Ian)
-        repmgr: report unreachable nodes when running "repmgr cluster (matrix|crosscheck);
-          GitHub #246 (Ian)
-        repmgr: add configuration file parameter "repmgr_bindir"; GitHub #246 (Ian)
-        repmgr: fix "Missing replication slots" label in "node check"; GitHub #507 (Ian)
-        repmgrd: fix parsing of -d/--daemonize option (Ian)
-        repmgrd: support "pausing" of repmgrd (Ian)
-
-4.1.1   2018-09-05
-        logging: explicitly log the text of failed queries as ERRORs to
-          assist logfile analysis; GitHub #498
-        repmgr: truncate version string, if necessary; GitHub #490 (Ian)
-        repmgr: improve messages emitted during "standby promote" (Ian)
-        repmgr: "standby clone" - don't copy external config files in --dry-run
-          mode; GitHub #491 (Ian)
-        repmgr: add "cluster_cleanup" event; GitHub #492 (Ian)
-        repmgr: (standby switchover) improve detection of free walsenders;
-          GitHub #495 (Ian)
-        repmgr: (node rejoin) improve replication slot handling; GitHub #499 (Ian)
-        repmgrd: ensure that sending SIGHUP always results in the log file
-          being reopened; GitHub #485 (Ian)
-        repmgrd: report version number *after* logger initialisation; GitHub #487 (Ian)
-        repmgrd: fix startup on witness node when local data is stale; GitHub #488/#489 (Ian)
-        repmgrd: improve cascaded standby failover handling; GitHub #480 (Ian)
-        repmgrd: improve reconnection handling (Ian)
-
-4.1.0   2018-07-31
-        repmgr: change default log_level to INFO, add documentation; GitHub #470 (Ian)
-        repmgr: add "--missing-slots" check to "repmgr node check" (Ian)
-        repmgr: improve command line error handling; GitHub #464 (Ian)
-        repmgr: fix "standby register --wait-sync" when no timeout provided (Ian)
-        repmgr: "cluster show" returns non-zero value if an issue encountered;
-          GitHub #456 (Ian)
-        repmgr: "node check" and "node status" returns non-zero value if an issue
-           encountered (Ian)
-        repmgr: add CSV output mode to "cluster event"; GitHub #471 (Ian)
-        repmgr: add -q/--quiet option to suppress non-error output; GitHub #468 (Ian)
-        repmgr: "node status" returns non-zero value if an issue encountered (Ian)
-        repmgr: enable "recovery_min_apply_delay" to be 0; GitHub #448 (Ian)
-        repmgr: "cluster cleanup" - add missing help options; GitHub #461/#462 (gclough)
-        repmgr: ensure witness node follows new primary after switchover;
-          GitHub #453 (Ian)
-        repmgr: fix witness node handling in "node check"/"node status";
-          GitHub #451 (Ian)
-        repmgr: fix "primary_slot_name" when using "standby clone" with --recovery-conf-only;
-          GitHub #474 (Ian)
-        repmgr: don't perform a switchover if an exclusive backup is running;
-          GitHub #476 (Martín)
-        repmgr: enable "witness unregister" to be run on any node; GitHub #472 (Ian)
-        repmgrd: create a PID file by default; GitHub #457 (Ian)
-        repmgrd: daemonize process by default; GitHub #458 (Ian)
-
-4.0.6   2018-06-14
-        repmgr: (witness register) prevent registration of a witness server with the
-          same name as an existing node (Ian)
-        repmgr: (standby follow) check node has actually connected to new primary
-          before reporting success; GitHub #444 (Ian)
-        repmgr: (standby clone) improve handling of external configuration file copying,
-          including consideration in --dry-run check; GitHub #443 (Ian)
-        repmgr: (standby clone) don't require presence of "user" parameter in
-          conninfo string; GitHub #437 (Ian)
-        repmgr: (standby clone) improve documentation of --recovery-conf-only
-          mode; GitHub #438 (Ian)
-        repmgr: (node rejoin) fix bug when parsing --config-files parameter;
-          GitHub #442 (Ian)
-        repmgr: when using --dry-run, force log level to INFO to ensure output
-          will always be displayed; GitHub #441 (Ian)
-        repmgr: (cluster matrix/crosscheck) return non-zero exit code if node
-           connection issues detected; GitHub #447 (Ian)
-        repmgrd: ensure local node is counted as quorum member; GitHub #439 (Ian)
-
-4.0.5   2018-05-02
-        repmgr: poll demoted primary after restart as a standby during a
-          switchover operation; GitHub #408 (Ian)
-        repmgr: add configuration parameter "config_directory"; GitHub #424 (Ian)
-        repmgr: add "dbname=replication" to all replication connection strings;
-          GitHub #421 (Ian)
-        repmgr: add sanity check if --upstream-node-id not supplied when executing
-          "standby register"; GitHub #395 (Ian)
-        repmgr: enable provision of "archive_cleanup_command" in recovery.conf;
-          GitHub #416 (Ian)
-        repmgr: actively check for node to rejoin cluster; GitHub #415 (Ian)
-        repmgr: enable pg_rewind to be used with PostgreSQL 9.3/9.4; GitHub #413 (Ian)
-        repmgr: fix minimum accepted value for "degraded_monitoring_timeout";
-          GitHub #411 (Ian)
-        repmgr: fix superuser password handling; GitHub #400 (Ian)
-        repmgr: fix parsing of "archive_ready_critical" configuration file
-          parameter; GitHub #426 (Ian)
-        repmgr: fix display of conninfo parsing error messages (Ian)
-        repmgr: fix "repmgr cluster crosscheck" output; GitHub #389 (Ian)
-        repmgrd: prevent standby connection handle from going stale (Ian)
-        repmgrd: fix memory leaks in witness code; GitHub #402 (AndrzejNowicki, Martín)
-        repmgrd: handle "pg_ctl promote" timeout; GitHub #425 (Ian)
-        repmgrd: handle failover situation with only two nodes in the primary
-          location, and at least one node in another location; GitHub #407 (Ian)
-        repmgrd: set "connect_timeout=2" when pinging a server (Ian)
-
-4.0.4   2018-03-09
-        repmgr: add "standby clone --recovery-conf-only" option; GitHub #382 (Ian)
-        repmgr: make "standby promote" timeout values configurable; GitHub #387 (Ian)
-        repmgr: improve replication slot warnings generated by "node status";
-          GitHub #385 (Ian)
-        repmgr: remove restriction on replication slots when cloning from
-          a Barman server; GitHub #379 (Ian)
-        repmgr: ensure "node rejoin" honours "--dry-run" option; GitHub #383 (Ian)
-        repmgr: fix --superuser handling when cloning a standby; GitHub #380 (Ian)
-        repmgr: update various help options; GitHub #391, #392 (hasegeli)
-        repmgrd: add event "repmgrd_shutdown"; GitHub #393 (Ian)
-        repmgrd: improve detection of status change from primary to standby (Ian)
-        repmgrd: improve log output in various situations (Ian)
-        repmgrd: improve reconnection to the local node after a failover (Ian)
-        repmgrd: ensure witness server connects to new primary after a failover (Ian)
-
-4.0.3   2018-02-15
-        repmgr: improve switchover handling when "pg_ctl" used to control the
-          server and logging output is not explicitly redirected (Ian)
-        repmgr: improve switchover log messages and exit code when old primary could
-          not be shut down cleanly (Ian)
-        repmgr: check demotion candidate can make a replication connection to the
-          promotion candidate before executing a switchover; GitHub #370 (Ian)
-        repmgr: add check for sufficient walsenders/replication slots before executing
-          a switchover; GitHub #371 (Ian)
-        repmgr: add --dry-run mode to "repmgr standby follow"; GitHub #368 (Ian)
-        repmgr: provide information about the primary node for "standby_register" and
-          "standby_follow" event notifications; GitHub #375 (Ian)
-        repmgr: add "standby_register_sync" event notification; GitHub #374 (Ian)
-        repmgr: output any connection error messages in "cluster show"'s list of
-          warnings; GitHub #369 (Ian)
-        repmgr: ensure an inactive data directory can be deleted; GitHub #366 (Ian)
-        repmgr: fix upstream node display in "repmgr node status"; GitHub #363 (fanf2)
-        repmgr: improve/clarify documentation and update --help output for
-          "primary unregister"; GitHub #373 (Ian)
-        repmgr: allow replication slots when Barman is configured; GitHub #379 (Ian)
-        repmgr: fix parsing of "pg_basebackup_options"; GitHub #376 (Ian)
-        repmgr: ensure "pg_subtrans" directory is created when cloning a standby in
-          Barman mode (Ian)
-        repmgr: fix primary node check in "witness register"; GitHub #377 (Ian)
-
-4.0.2   2018-01-18
-        repmgr: add missing -W option to getopt_long() invocation; GitHub #350 (Ian)
-        repmgr: automatically create slot name if missing; GitHub #343 (Ian)
-        repmgr: fixes to parsing output of remote repmgr invocations; GitHub #349 (Ian)
-        repmgr: BDR support - create missing connection replication set
-          if required; GitHub #347 (Ian)
-        repmgr: handle missing node record in "repmgr node rejoin"; GitHub #358 (Ian)
-        repmgr: enable documentation to be build as single HTML file; GitHub #353 (fanf2)
-        repmgr: recognize "--terse" option for "repmgr cluster event"; GitHub #360 (Ian)
-        repmgr: add "--wait-start" option for "repmgr standby register"; GitHub #356 (Ian)
-        repmgr: add "%p" event notification parameter for "repmgr standby switchover"
-          containing the node ID of the demoted primary (Ian)
-        docs: various fixes and updates (Ian, Daymel, Martín, ams)
-
-4.0.1   2017-12-13
-        repmgr: ensure "repmgr node check --action=" returns appropriate return
-          code; GitHub #340 (Ian)
-        repmgr: add missing schema qualification in get_all_node_records_with_upstream()
-          query GitHub #341 (Martín)
-        repmgr: initialise "voting_term" table in application, not extension SQL;
-          GitHub #344 (Ian)
-        repmgr: delete any replication slots copied by pg_rewind; GitHub #334 (Ian)
-        repmgr: fix configuration file sanity check; GitHub #342 (Ian)
-
-4.0.0   2017-11-21
-        Complete rewrite with many changes; for details see the repmgr 4.0.0 release
-        notes at: https://repmgr.org/docs/4.0/release-4.0.0.html
 
 3.3.2   2017-06-01
         Add support for PostgreSQL 10 (Ian)

Makefile.global.in

@@ -2,7 +2,6 @@
 # Makefile.global.in
 # @configure_input@
 
-
 # Can only be built using pgxs
 USE_PGXS=1
 
@@ -15,26 +14,14 @@ ifeq ($(vpath_build),yes)
 	VPATH := $(repmgr_abs_srcdir)/$(repmgr_subdir)
 	USE_VPATH :=$(VPATH)
 endif
-
-SED=@SED@
-
 GIT_WORK_TREE=${repmgr_abs_srcdir}
 GIT_DIR=${repmgr_abs_srcdir}/.git
 export GIT_DIR
 export GIT_WORK_TREE
-PG_LDFLAGS=-lcurl -ljson-c
+
 include $(PGXS)
 
 -include ${repmgr_abs_srcdir}/Makefile.custom
 
 REPMGR_VERSION=$(shell awk '/^\#define REPMGR_VERSION / { print $3; }' ${repmgr_abs_srcdir}/repmgr_version.h.in | cut -d '"' -f 2)
-REPMGR_RELEASE_DATE=$(shell awk '/^\#define REPMGR_RELEASE_DATE / { print $3; }' ${repmgr_abs_srcdir}/repmgr_version.h.in | cut -d '"' -f 2)
 
-FLEX = flex
-
-##########################################################################
-#
-# Global targets and rules
-
-%.c: %.l
-	$(FLEX) $(FLEXFLAGS) -o'$@' $<

Makefile.in

@@ -11,30 +11,7 @@ EXTENSION = repmgr
 
 DATA = \
   repmgr--unpackaged--4.0.sql \
-  repmgr--unpackaged--5.1.sql \
+  repmgr--4.0.sql
-  repmgr--unpackaged--5.2.sql \
-  repmgr--unpackaged--5.3.sql \
-  repmgr--4.0.sql \
-  repmgr--4.0--4.1.sql \
-  repmgr--4.1.sql \
-  repmgr--4.1--4.2.sql \
-  repmgr--4.2.sql \
-  repmgr--4.2--4.3.sql \
-  repmgr--4.3.sql \
-  repmgr--4.3--4.4.sql \
-  repmgr--4.4.sql \
-  repmgr--4.4--5.0.sql \
-  repmgr--5.0.sql \
-  repmgr--5.0--5.1.sql \
-  repmgr--5.1.sql \
-  repmgr--5.1--5.2.sql \
-  repmgr--5.2.sql \
-  repmgr--5.2--5.3.sql \
-  repmgr--5.3.sql \
-  repmgr--5.3--5.4.sql \
-  repmgr--5.4.sql \
-  repmgr--5.4--5.5.sql \
-  repmgr--5.5.sql
 
 REGRESS = repmgr_extension
 
@@ -49,36 +26,24 @@ all: \
 PG_CPPFLAGS = -std=gnu89 -I$(includedir_internal) -I$(libpq_srcdir) -Wall -Wmissing-prototypes -Wmissing-declarations $(EXTRA_CFLAGS)
 SHLIB_LINK = $(libpq)
 
-
+HEADERS = $(wildcard *.h)
 
 OBJS = \
 	repmgr.o
 
 include Makefile.global
 
-ifeq ($(vpath_build),yes)
-	HEADERS = $(wildcard *.h)
-else
-	HEADERS_built = $(wildcard *.h)
-endif
 
 $(info Building against PostgreSQL $(MAJORVERSION))
 
 REPMGR_CLIENT_OBJS = repmgr-client.o \
-	repmgr-action-primary.o repmgr-action-standby.o repmgr-action-witness.o \
+	repmgr-action-primary.o repmgr-action-standby.o repmgr-action-bdr.o repmgr-action-cluster.o repmgr-action-node.o \
-	repmgr-action-cluster.o repmgr-action-node.o repmgr-action-service.o repmgr-action-daemon.o \
+	configfile.o log.o strutil.o controldata.o dirutil.o compat.o dbutils.o
-	configdata.o configfile.o configfile-scan.o log.o strutil.o controldata.o dirutil.o compat.o \
+REPMGRD_OBJS = repmgrd.o repmgrd-physical.o repmgrd-bdr.o configfile.o log.o dbutils.o strutil.o controldata.o
-	dbutils.o sysutils.o pgbackupapi.o
-REPMGRD_OBJS = repmgrd.o repmgrd-physical.o configdata.o configfile.o configfile-scan.o log.o \
-	dbutils.o strutil.o controldata.o compat.o sysutils.o
-
 DATE=$(shell date "+%Y-%m-%d")
 
 repmgr_version.h: repmgr_version.h.in
-	$(SED) -E 's/REPMGR_VERSION_DATE.*""/REPMGR_VERSION_DATE "$(DATE)"/' $< >$@; \
+	sed '0,/REPMGR_VERSION_DATE/s,\(REPMGR_VERSION_DATE\).*,\1 "$(DATE)",' $< >$@
-	$(SED) -i -E 's/PG_ACTUAL_VERSION_NUM/PG_ACTUAL_VERSION_NUM $(VERSION_NUM)/' $@
-
-configfile-scan.c: configfile-scan.l
 
 $(REPMGR_CLIENT_OBJS): repmgr-client.h repmgr_version.h
 
@@ -98,37 +63,32 @@ Makefile: Makefile.in config.status configure
 Makefile.global: Makefile.global.in config.status configure
 	./config.status $@
 
-doc: repmgr_version.h
-	$(MAKE) -C doc html
-
-doc-repmgr.html: repmgr_version.h
-	$(MAKE) -C doc repmgr.html
-
-doc-repmgr-A4.pdf: repmgr_version.h
-	$(MAKE) -C doc repmgr-A4.pdf
-
-doc-repmgr-US.pdf: repmgr_version.h
-	$(MAKE) -C doc repmgr-US.pdf
-
-install-doc: doc
-	$(MAKE) -C doc install
-
 clean: additional-clean
 
 maintainer-clean: additional-maintainer-clean
 
 additional-clean:
-	rm -f *.o
+	rm -f repmgr-client.o
-	rm -f repmgr_version.h
+	rm -f repmgr-action-primary.o
-	$(MAKE) -C doc clean
+	rm -f repmgr-action-standby.o
+	rm -f repmgr-action-bdr.o
+	rm -f repmgr-action-node.o
+	rm -f repmgr-action-cluster.o
+	rm -f repmgrd.o
+	rm -f repmgrd-physical.o
+	rm -f repmgrd-bdr.o
+	rm -f compat.o
+	rm -f configfile.o
+	rm -f controldata.o
+	rm -f dbutils.o
+	rm -f dirutil.o
+	rm -f log.o
+	rm -f strutil.o
 
-additional-maintainer-clean: clean
+maintainer-additional-clean: clean
-	$(MAKE) -C doc maintainer-clean
+	rm -f configure
 	rm -f config.status config.log
-	rm -f config.h
-	rm -f repmgr_version.h
 	rm -f Makefile
-	rm -f Makefile.global
 	@rm -rf autom4te.cache/
 
 ifeq ($(MAJORVERSION),$(filter $(MAJORVERSION),9.3 9.4))
@@ -143,4 +103,3 @@ installdirs-scripts:
 .PHONY: installdirs-scripts
 endif
 
-.PHONY: doc doc-repmgr.html doc-repmgr-A4.pdf doc-repmgr-US.pdf install-doc

TODO.md

@@ -1,20 +0,0 @@
-TODO
-====
-
-This file contains a list of improvements which are desirable and/or have
-been requested, and which we aim to address/implement when time and resources
-permit.
-
-It is *not* a roadmap and there's no guarantee of any item being implemented
-within any given timeframe.
-
-
-Enable suspension of repmgrd failover
--------------------------------------
-
-When performing maintenance, e.g. a switchover, it's necessary to stop all
-repmgrd nodes to prevent unintended failover; this is obviously inconvenient.
-We'll need to implement some way of notifying each repmgrd to suspend automatic
-failover until further notice.
-
-Requested in GitHub #410 ( https://github.com/EnterpriseDB/repmgr/issues/410 )

compat.c

@@ -6,7 +6,7 @@
  *    supported PostgreSQL versions. They're unlikely to change but
  *    it would be worth keeping an eye on them for any fixes/improvements.
  *
- * Copyright (c) EnterpriseDB Corporation, 2010-2021
+ * Copyright (c) 2ndQuadrant, 2010-2017
  *
  * Portions Copyright (c) 1996-2013, PostgreSQL Global Development Group
  * Portions Copyright (c) 1994, Regents of the University of California
@@ -98,42 +98,9 @@ appendShellString(PQExpBuffer buf, const char *str)
 
 		if (*p == '\'')
 			appendPQExpBufferStr(buf, "'\"'\"'");
-		else if (*p == '&')
-			appendPQExpBufferStr(buf, "\\&");
 		else
 			appendPQExpBufferChar(buf, *p);
 	}
 
 	appendPQExpBufferChar(buf, '\'');
 }
-
-/*
- * Adapted from: src/fe_utils/string_utils.c
- */
-void
-appendRemoteShellString(PQExpBuffer buf, const char *str)
-{
-	const char *p;
-
-	appendPQExpBufferStr(buf, "\\'");
-
-	for (p = str; *p; p++)
-	{
-		if (*p == '\n' || *p == '\r')
-		{
-			fprintf(stderr,
-					_("shell command argument contains a newline or carriage return: \"%s\"\n"),
-					str);
-			exit(ERR_BAD_CONFIG);
-		}
-
-		if (*p == '\'')
-			appendPQExpBufferStr(buf, "'\"'\"'");
-		else if (*p == '&')
-			appendPQExpBufferStr(buf, "\\&");
-		else
-			appendPQExpBufferChar(buf, *p);
-	}
-
-	appendPQExpBufferStr(buf, "\\'");
-}

compat.h

@@ -1,6 +1,6 @@
 /*
  * compat.h
- * Copyright (c) EnterpriseDB Corporation, 2010-2021
+ * Copyright (c) 2ndQuadrant, 2010-2017
  *
  * Portions Copyright (c) 1996-2013, PostgreSQL Global Development Group
  * Portions Copyright (c) 1994, Regents of the University of California
@@ -27,6 +27,4 @@ extern void appendConnStrVal(PQExpBuffer buf, const char *str);
 
 extern void appendShellString(PQExpBuffer buf, const char *str);
 
-extern void appendRemoteShellString(PQExpBuffer buf, const char *str);
-
 #endif

config.h.in

@@ -1,2 +1,4 @@
 /* config.h.in.  Generated from configure.in by autoheader.  */
 
+/* Only build repmgr for BDR */
+#undef BDR_ONLY

configdata.c

@@ -1,986 +0,0 @@
-/*
- * configdata.c - contains structs with parsed configuration data
- *
- * Copyright (c) EnterpriseDB Corporation, 2010-2021
- *
- * This program is free software: you can redistribute it and/or modify
- * it under the terms of the GNU General Public License as published by
- * the Free Software Foundation, either version 3 of the License, or
- * (at your option) any later version.
- *
- * This program is distributed in the hope that it will be useful,
- * but WITHOUT ANY WARRANTY; without even the implied warranty of
- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
- * GNU General Public License for more details.
- *
- * You should have received a copy of the GNU General Public License
- * along with this program.  If not, see <http://www.gnu.org/licenses/>.
- */
-
-#include "repmgr.h"
-#include "configfile.h"
-
-/*
- * Parsed configuration settings are stored here
- */
-t_configuration_options config_file_options;
-
-
-/*
- * Configuration settings are defined here
- */
-
-struct ConfigFileSetting config_file_settings[] =
-{
-
-	/* ================
-	 * node information
-	 * ================
-	 */
-	/* node_id */
-	{
-		"node_id",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.node_id },
-		{ .intdefault = UNKNOWN_NODE_ID },
-		{ .intminval = MIN_NODE_ID },
-		{},
-		{}
-	},
-	/* node_name */
-	{
-		"node_name",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.node_name },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.node_name) },
-		{}
-	},
-	/* conninfo */
-	{
-		"conninfo",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.conninfo },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.conninfo) },
-		{}
-	},
-	/* replication_user */
-	{
-		"replication_user",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.replication_user },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.replication_user) },
-		{}
-	},
-	/* data_directory */
-	{
-		"data_directory",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.data_directory },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.data_directory) },
-		{ .postprocess_func = &repmgr_canonicalize_path }
-	},
-	/* config_directory */
-	{
-		"config_directory",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.config_directory },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.config_directory) },
-		{ .postprocess_func = &repmgr_canonicalize_path }
-	},
-	/* pg_bindir */
-	{
-		"pg_bindir",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.pg_bindir },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.pg_bindir) },
-		{ .postprocess_func = &repmgr_canonicalize_path }
-	},
-	/* repmgr_bindir */
-	{
-		"repmgr_bindir",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.repmgr_bindir },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.repmgr_bindir) },
-		{ .postprocess_func = &repmgr_canonicalize_path }
-	},
-	/* replication_type */
-	{
-		"replication_type",
-		CONFIG_REPLICATION_TYPE,
-		{ .replicationtypeptr = &config_file_options.replication_type },
-		{ .replicationtypedefault = DEFAULT_REPLICATION_TYPE },
-		{},
-		{},
-		{}
-	},
-
-	/* ================
-	 * logging settings
-	 * ================
-	 */
-
-	/*
-	 * log_level
-	 * NOTE: the default for "log_level" is set in log.c and does not need
-	 * to be initialised here
-	 */
-	{
-		"log_level",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.log_level },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.log_level) },
-		{}
-	},
-	/* log_facility */
-	{
-		"log_facility",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.log_facility },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.log_facility) },
-		{}
-	},
-	/* log_file */
-	{
-		"log_file",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.log_file },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.log_file) },
-		{ .postprocess_func = &repmgr_canonicalize_path }
-	},
-	/* log_status_interval */
-	{
-		"log_status_interval",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.log_status_interval },
-		{ .intdefault = DEFAULT_LOG_STATUS_INTERVAL, },
-		{ .intminval = 0 },
-		{},
-		{}
-	},
-	/* ======================
-	 * standby clone settings
-	 * ======================
-	 */
-	/* use_replication_slots */
-	{
-		"use_replication_slots",
-		CONFIG_BOOL,
-		{ .boolptr = &config_file_options.use_replication_slots },
-		{ .booldefault = DEFAULT_USE_REPLICATION_SLOTS },
-		{},
-		{},
-		{}
-	},
-	/* pg_basebackup_options */
-	{
-		"pg_basebackup_options",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.pg_basebackup_options },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.pg_basebackup_options) },
-		{}
-	},
-	/* restore_command */
-	{
-		"restore_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.restore_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.restore_command) },
-		{}
-	},
-	/* tablespace_mapping */
-	{
-		"tablespace_mapping",
-		CONFIG_TABLESPACE_MAPPING,
-		{ .tablespacemappingptr = &config_file_options.tablespace_mapping },
-		{},
-		{},
-		{},
-		{}
-	},
-	/* recovery_min_apply_delay */
-	{
-		"recovery_min_apply_delay",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.recovery_min_apply_delay },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.recovery_min_apply_delay) },
-        {
-			.process_func = &parse_time_unit_parameter,
-			.providedptr = &config_file_options.recovery_min_apply_delay_provided
-		}
-	},
-
-	/* archive_cleanup_command */
-	{
-		"archive_cleanup_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.archive_cleanup_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.archive_cleanup_command) },
-		{}
-	},
-
-	/* use_primary_conninfo_password */
-	{
-		"use_primary_conninfo_password",
-		CONFIG_BOOL,
-		{ .boolptr = &config_file_options.use_primary_conninfo_password },
-		{ .booldefault = DEFAULT_USE_PRIMARY_CONNINFO_PASSWORD },
-		{},
-		{},
-		{}
-	},
-	/* passfile */
-	{
-		"passfile",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.passfile },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.passfile) },
-		{}
-	},
-
-	/* ======================
-	 * standby clone settings
-	 * ======================
-	 */
-	/* promote_check_timeout */
-	{
-		"promote_check_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.promote_check_timeout },
-		{ .intdefault = DEFAULT_PROMOTE_CHECK_TIMEOUT },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* promote_check_interval */
-	{
-		"promote_check_interval",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.promote_check_interval },
-		{ .intdefault = DEFAULT_PROMOTE_CHECK_INTERVAL },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* pg_backupapi_backup_id*/
-	{
-		"pg_backupapi_backup_id",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.pg_backupapi_backup_id },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.pg_backupapi_backup_id) },
-		{}
-	},
-	/* pg_backupapi_host*/
-	{
-		"pg_backupapi_host",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.pg_backupapi_host },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.pg_backupapi_host) },
-		{}
-	},
-	/* pg_backupapi_node_name */
-	{
-		"pg_backupapi_node_name",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.pg_backupapi_node_name },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.pg_backupapi_node_name) },
-		{}
-	},
-	/* pg_backupapi_remote_ssh_command */
-	{
-		"pg_backupapi_remote_ssh_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.pg_backupapi_remote_ssh_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.pg_backupapi_remote_ssh_command) },
-		{}
-	},
-
-	/* =======================
-	 * standby follow settings
-	 * =======================
-	 */
-	/* primary_follow_timeout */
-	{
-		"primary_follow_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.primary_follow_timeout },
-		{ .intdefault = DEFAULT_PRIMARY_FOLLOW_TIMEOUT, },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* standby_follow_timeout */
-	{
-		"standby_follow_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.standby_follow_timeout },
-		{ .intdefault = DEFAULT_STANDBY_FOLLOW_TIMEOUT },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* standby_follow_restart */
-	{
-		"standby_follow_restart",
-		CONFIG_BOOL,
-		{ .boolptr = &config_file_options.standby_follow_restart },
-		{ .booldefault = DEFAULT_STANDBY_FOLLOW_RESTART },
-		{},
-		{},
-		{}
-	},
-
-	/* ===========================
-	 * standby switchover settings
-	 * ===========================
-	 */
-	/* shutdown_check_timeout */
-	{
-		"shutdown_check_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.shutdown_check_timeout },
-		{ .intdefault = DEFAULT_SHUTDOWN_CHECK_TIMEOUT },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* standby_reconnect_timeout */
-	{
-		"standby_reconnect_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.standby_reconnect_timeout },
-		{ .intdefault = DEFAULT_STANDBY_RECONNECT_TIMEOUT },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* wal_receive_check_timeout */
-	{
-		"wal_receive_check_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.wal_receive_check_timeout },
-		{ .intdefault = DEFAULT_WAL_RECEIVE_CHECK_TIMEOUT },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-
-	/* ====================
-	 * node rejoin settings
-	 * ====================
-	 */
-	/* node_rejoin_timeout */
-	{
-		"node_rejoin_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.node_rejoin_timeout },
-		{ .intdefault = DEFAULT_NODE_REJOIN_TIMEOUT },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* ===================
-	 * node check settings
-	 * ===================
-	 */
-	/* archive_ready_warning */
-	{
-		"archive_ready_warning",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.archive_ready_warning },
-		{ .intdefault = DEFAULT_ARCHIVE_READY_WARNING },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* archive_ready_critical */
-	{
-		"archive_ready_critical",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.archive_ready_critical },
-		{ .intdefault = DEFAULT_ARCHIVE_READY_CRITICAL },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* replication_lag_warning */
-	{
-		"replication_lag_warning",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.replication_lag_warning },
-		{ .intdefault = DEFAULT_REPLICATION_LAG_WARNING },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* replication_lag_critical */
-	{
-		"replication_lag_critical",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.replication_lag_critical },
-		{ .intdefault = DEFAULT_REPLICATION_LAG_CRITICAL },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-
-	/* ================
-	 * witness settings
-	 * ================
-	 */
-	/* witness_sync_interval */
-	{
-		"witness_sync_interval",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.witness_sync_interval },
-		{ .intdefault = DEFAULT_WITNESS_SYNC_INTERVAL },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-
-	/* ================
-	 * repmgrd settings
-	 * ================
-	 */
-	/* failover */
-	{
-		"failover",
-		CONFIG_FAILOVER_MODE,
-		{ .failovermodeptr = &config_file_options.failover },
-		{ .failovermodedefault = FAILOVER_MANUAL },
-		{},
-		{},
-		{}
-	},
-	/* location */
-	{
-		"location",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.location },
-		{ .strdefault = DEFAULT_LOCATION },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.location) },
-		{}
-	},
-	/* priority */
-	{
-		"priority",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.priority },
-		{ .intdefault = DEFAULT_PRIORITY, },
-		{ .intminval = 0 },
-		{},
-		{}
-	},
-	/* promote_command */
-	{
-		"promote_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.promote_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.promote_command) },
-		{}
-	},
-	/* follow_command */
-	{
-		"follow_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.follow_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.follow_command) },
-		{}
-	},
-	/* monitor_interval_secs */
-	{
-		"monitor_interval_secs",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.monitor_interval_secs },
-		{ .intdefault = DEFAULT_MONITORING_INTERVAL },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* reconnect_attempts */
-	{
-		"reconnect_attempts",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.reconnect_attempts },
-		{ .intdefault = DEFAULT_RECONNECTION_ATTEMPTS },
-		{ .intminval = 0 },
-		{},
-		{}
-	},
-	/* reconnect_interval */
-	{
-		"reconnect_interval",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.reconnect_interval },
-		{ .intdefault = DEFAULT_RECONNECTION_INTERVAL },
-		{ .intminval = 0 },
-		{},
-		{}
-	},
-
-	/* monitoring_history */
-	{
-		"monitoring_history",
-		CONFIG_BOOL,
-		{ .boolptr = &config_file_options.monitoring_history },
-		{ .booldefault = DEFAULT_MONITORING_HISTORY },
-		{},
-		{},
-		{}
-	},
-	/* degraded_monitoring_timeout */
-	{
-		"degraded_monitoring_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.degraded_monitoring_timeout },
-		{ .intdefault = DEFAULT_DEGRADED_MONITORING_TIMEOUT },
-		{ .intminval = -1 },
-		{},
-		{}
-	},
-	/* async_query_timeout */
-	{
-		"async_query_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.async_query_timeout },
-		{ .intdefault = DEFAULT_ASYNC_QUERY_TIMEOUT },
-		{ .intminval = 0 },
-		{},
-		{}
-	},
-	/* primary_notification_timeout */
-	{
-		"primary_notification_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.primary_notification_timeout },
-		{ .intdefault = DEFAULT_PRIMARY_NOTIFICATION_TIMEOUT },
-		{ .intminval = 0 },
-		{},
-		{}
-	},
-	/* repmgrd_standby_startup_timeout */
-	{
-		"repmgrd_standby_startup_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.repmgrd_standby_startup_timeout },
-		{ .intdefault = DEFAULT_REPMGRD_STANDBY_STARTUP_TIMEOUT },
-		{ .intminval = 0 },
-		{},
-		{}
-	},
-	/* repmgrd_pid_file */
-	{
-		"repmgrd_pid_file",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.repmgrd_pid_file },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.repmgrd_pid_file) },
-		{ .postprocess_func = &repmgr_canonicalize_path }
-	},
-	/* repmgrd_exit_on_inactive_node */
-	{
-		"repmgrd_exit_on_inactive_node",
-		CONFIG_BOOL,
-		{ .boolptr = &config_file_options.repmgrd_exit_on_inactive_node},
-		{ .booldefault = DEFAULT_REPMGRD_EXIT_ON_INACTIVE_NODE },
-		{},
-		{},
-		{}
-	},
-	/* standby_disconnect_on_failover */
-	{
-		"standby_disconnect_on_failover",
-		CONFIG_BOOL,
-		{ .boolptr = &config_file_options.standby_disconnect_on_failover },
-		{ .booldefault = DEFAULT_STANDBY_DISCONNECT_ON_FAILOVER },
-		{},
-		{},
-		{}
-	},
-	/* sibling_nodes_disconnect_timeout */
-	{
-		"sibling_nodes_disconnect_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.sibling_nodes_disconnect_timeout },
-		{ .intdefault = DEFAULT_SIBLING_NODES_DISCONNECT_TIMEOUT },
-		{ .intminval = 0 },
-		{},
-		{}
-	},
-	/* connection_check_type */
-	{
-		"connection_check_type",
-		CONFIG_CONNECTION_CHECK_TYPE,
-		{ .checktypeptr = &config_file_options.connection_check_type },
-		{ .checktypedefault = DEFAULT_CONNECTION_CHECK_TYPE },
-		{},
-		{},
-		{}
-	},
-	/* primary_visibility_consensus */
-	{
-		"primary_visibility_consensus",
-		CONFIG_BOOL,
-		{ .boolptr = &config_file_options.primary_visibility_consensus },
-		{ .booldefault = DEFAULT_PRIMARY_VISIBILITY_CONSENSUS },
-		{},
-		{},
-		{}
-	},
-	/* always_promote */
-	{
-		"always_promote",
-		CONFIG_BOOL,
-		{ .boolptr = &config_file_options.always_promote },
-		{ .booldefault = DEFAULT_ALWAYS_PROMOTE },
-		{},
-		{},
-		{}
-	},
-	/* failover_validation_command */
-	{
-		"failover_validation_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.failover_validation_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.failover_validation_command) },
-		{}
-	},
-	/* election_rerun_interval */
-	{
-		"election_rerun_interval",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.election_rerun_interval },
-		{ .intdefault = DEFAULT_ELECTION_RERUN_INTERVAL },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* child_nodes_check_interval */
-	{
-		"child_nodes_check_interval",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.child_nodes_check_interval },
-		{ .intdefault = DEFAULT_CHILD_NODES_CHECK_INTERVAL },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* child_nodes_disconnect_min_count */
-	{
-		"child_nodes_disconnect_min_count",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.child_nodes_disconnect_min_count },
-		{ .intdefault = DEFAULT_CHILD_NODES_DISCONNECT_MIN_COUNT },
-		{ .intminval = -1 },
-		{},
-		{}
-	},
-	/* child_nodes_connected_min_count */
-	{
-		"child_nodes_connected_min_count",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.child_nodes_connected_min_count },
-		{ .intdefault = DEFAULT_CHILD_NODES_CONNECTED_MIN_COUNT},
-		{ .intminval = -1 },
-		{},
-		{}
-	},
-	/* child_nodes_connected_include_witness */
-	{
-		"child_nodes_connected_include_witness",
-		CONFIG_BOOL,
-		{ .boolptr = &config_file_options.child_nodes_connected_include_witness },
-		{ .booldefault = DEFAULT_CHILD_NODES_CONNECTED_INCLUDE_WITNESS },
-		{},
-		{},
-		{}
-	},
-	/* child_nodes_disconnect_timeout */
-	{
-		"child_nodes_disconnect_timeout",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.child_nodes_disconnect_timeout },
-		{ .intdefault = DEFAULT_CHILD_NODES_DISCONNECT_TIMEOUT },
-		{ .intminval = 0 },
-		{},
-		{}
-	},
-	/* child_nodes_disconnect_command */
-	{
-		"child_nodes_disconnect_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.child_nodes_disconnect_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.child_nodes_disconnect_command) },
-		{}
-	},
-	/* ================
-	 * service settings
-	 * ================
-	 */
-	/* pg_ctl_options */
-	{
-		"pg_ctl_options",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.pg_ctl_options },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.pg_ctl_options) },
-		{}
-	},
-	/* service_start_command */
-	{
-		"service_start_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.service_start_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.service_start_command) },
-		{}
-	},
-	/* service_stop_command */
-	{
-		"service_stop_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.service_stop_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.service_stop_command) },
-		{}
-	},
-	/* service_restart_command */
-	{
-		"service_restart_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.service_restart_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.service_restart_command) },
-		{}
-	},
-	/* service_reload_command */
-	{
-		"service_reload_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.service_reload_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.service_reload_command) },
-		{}
-	},
-	/* service_promote_command */
-	{
-		"service_promote_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.service_promote_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.service_promote_command) },
-		{}
-	},
-
-	/* ========================
-	 * repmgrd service settings
-	 * ========================
-	 */
-	/* repmgrd_service_start_command */
-	{
-		"repmgrd_service_start_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.repmgrd_service_start_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.repmgrd_service_start_command) },
-		{}
-	},
-	/* repmgrd_service_stop_command */
-	{
-		"repmgrd_service_stop_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.repmgrd_service_stop_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.repmgrd_service_stop_command) },
-		{}
-	},
-	/* ===========================
-	 * event notification settings
-	 * ===========================
-	 */
-	/* event_notification_command */
-	{
-		"event_notification_command",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.event_notification_command },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.event_notification_command) },
-		{}
-	},
-	{
-		"event_notifications",
-		CONFIG_EVENT_NOTIFICATION_LIST,
-		{ .notificationlistptr = &config_file_options.event_notifications },
-		{},
-		{},
-		{},
-		{}
-	},
-	/* ===============
-	 * barman settings
-	 * ===============
-	 */
-	/* barman_host */
-	{
-		"barman_host",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.barman_host },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.barman_host) },
-		{}
-	},
-	/* barman_server */
-	{
-		"barman_server",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.barman_server },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.barman_server) },
-		{}
-	},
-	/* barman_config */
-	{
-		"barman_config",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.barman_config },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.barman_config) },
-		{}
-	},
-	/* ==================
-	 * rsync/ssh settings
-	 * ==================
-	 */
-	/* rsync_options */
-	{
-		"rsync_options",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.rsync_options },
-		{ .strdefault = "" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.rsync_options) },
-		{}
-	},
-	/* ssh_options */
-	{
-		"ssh_options",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.ssh_options },
-		{ .strdefault = DEFAULT_SSH_OPTIONS },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.ssh_options) },
-		{}
-	},
-	/* ==================================
-	 * undocumented experimental settings
-	 * ==================================
-	 */
-	/* reconnect_loop_sync */
-	{
-		"reconnect_loop_sync",
-		CONFIG_BOOL,
-		{ .boolptr = &config_file_options.reconnect_loop_sync },
-		{ .booldefault = false },
-		{},
-		{},
-		{}
-	},
-	/* ==========================
-	 * undocumented test settings
-	 * ==========================
-	 */
-	/* promote_delay */
-	{
-		"promote_delay",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.promote_delay },
-		{ .intdefault = 0 },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	/* failover_delay */
-	{
-		"failover_delay",
-		CONFIG_INT,
-		{ .intptr = &config_file_options.failover_delay },
-		{ .intdefault = 0 },
-		{ .intminval = 1 },
-		{},
-		{}
-	},
-	{
-		"connection_check_query",
-		CONFIG_STRING,
-		{ .strptr = config_file_options.connection_check_query },
-		{ .strdefault = "SELECT 1" },
-		{},
-		{ .strmaxlen = sizeof(config_file_options.connection_check_query) },
-		{}
-	},
-	/* End-of-list marker */
-	{
-		NULL, CONFIG_INT, {}, {}, {}, {}, {}
-	}
-};
-

configfile-scan.l

@@ -1,644 +0,0 @@
-/*
- * Scanner for the configuration file
- */
-
-%{
-
-#include <setjmp.h>
-#include <sys/stat.h>
-#include <dirent.h>
-
-#include "repmgr.h"
-#include "configfile.h"
-
-/*
- * flex emits a yy_fatal_error() function that it calls in response to
- * critical errors like malloc failure, file I/O errors, and detection of
- * internal inconsistency.  That function prints a message and calls exit().
- * Mutate it to instead call our handler, which jumps out of the parser.
- */
-#undef fprintf
-#define fprintf(file, fmt, msg) CONF_flex_fatal(msg)
-
-enum
-{
-	CONF_ID = 1,
-	CONF_STRING = 2,
-	CONF_INTEGER = 3,
-	CONF_REAL = 4,
-	CONF_EQUALS = 5,
-	CONF_UNQUOTED_STRING = 6,
-	CONF_QUALIFIED_ID = 7,
-	CONF_EOL = 99,
-	CONF_ERROR = 100
-};
-
-static unsigned int ConfigFileLineno;
-static const char *CONF_flex_fatal_errmsg;
-static sigjmp_buf *CONF_flex_fatal_jmp;
-
-static char *CONF_scanstr(const char *s);
-static int	CONF_flex_fatal(const char *msg);
-
-static bool ProcessConfigFile(const char *base_dir, const char *config_file, const char *calling_file, bool strict, int depth, KeyValueList *contents, ItemList *error_list, ItemList *warning_list);
-
-static bool ProcessConfigFp(FILE *fp, const char *config_file, const char *calling_file, int depth, const char *base_dir, KeyValueList *contents, ItemList *error_list, ItemList *warning_list);
-
-static bool ProcessConfigDirectory(const char *base_dir, const char *includedir, const char *calling_file, int depth, KeyValueList *contents, ItemList *error_list, ItemList *warning_list);
-
-static char *AbsoluteConfigLocation(const char *base_dir, const char *location, const char *calling_file);
-
-%}
-
-%option 8bit
-%option never-interactive
-%option nodefault
-%option noinput
-%option nounput
-%option noyywrap
-%option warn
-%option prefix="CONF_yy"
-
-
-SIGN			("-"|"+")
-DIGIT			[0-9]
-HEXDIGIT		[0-9a-fA-F]
-
-UNIT_LETTER		[a-zA-Z]
-
-INTEGER			{SIGN}?({DIGIT}+|0x{HEXDIGIT}+){UNIT_LETTER}*
-
-EXPONENT		[Ee]{SIGN}?{DIGIT}+
-REAL			{SIGN}?{DIGIT}*"."{DIGIT}*{EXPONENT}?
-
-LETTER			[A-Za-z_\200-\377]
-LETTER_OR_DIGIT [A-Za-z_0-9\200-\377]
-
-ID				{LETTER}{LETTER_OR_DIGIT}*
-QUALIFIED_ID	{ID}"."{ID}
-
-UNQUOTED_STRING {LETTER}({LETTER_OR_DIGIT}|[-._:/])*
-STRING			\'([^'\\\n]|\\.|\'\')*\'
-
-%%
-
-\n				ConfigFileLineno++; return CONF_EOL;
-[ \t\r]+		/* eat whitespace */
-#.*				/* eat comment (.* matches anything until newline) */
-
-{ID}			return CONF_ID;
-{QUALIFIED_ID}	return CONF_QUALIFIED_ID;
-{STRING}		return CONF_STRING;
-{UNQUOTED_STRING} return CONF_UNQUOTED_STRING;
-{INTEGER}		return CONF_INTEGER;
-{REAL}			return CONF_REAL;
-=				return CONF_EQUALS;
-
-.				return CONF_ERROR;
-
-%%
-
-
-extern bool
-ProcessRepmgrConfigFile(const char *config_file, const char *base_dir, ItemList *error_list, ItemList *warning_list)
-{
-	return ProcessConfigFile(base_dir, config_file, NULL, true, 0, NULL, error_list, warning_list);
-}
-
-
-extern bool
-ProcessPostgresConfigFile(const char *config_file, const char *base_dir, bool strict, KeyValueList *contents, ItemList *error_list, ItemList *warning_list)
-{
-	return ProcessConfigFile(base_dir, config_file, NULL, strict, 0, contents, error_list, warning_list);
-}
-
-static bool
-ProcessConfigFile(const char *base_dir, const char *config_file, const char *calling_file, bool strict, int depth, KeyValueList *contents, ItemList *error_list, ItemList *warning_list)
-{
-	char	   *abs_path;
-	bool		success = true;
-	FILE	   *fp;
-
-	/*
-	 * Reject file name that is all-blank (including empty), as that leads to
-	 * confusion --- we'd try to read the containing directory as a file.
-	 */
-	if (strspn(config_file, " \t\r\n") == strlen(config_file))
-	{
-		return false;
-	}
-
-	/*
-	 * Reject too-deep include nesting depth.  This is just a safety check to
-	 * avoid dumping core due to stack overflow if an include file loops back
-	 * to itself.  The maximum nesting depth is pretty arbitrary.
-	 */
-	if (depth > 10)
-	{
-		item_list_append_format(error_list,
-								_("could not open configuration file \"%s\": maximum nesting depth exceeded"),
-								config_file);
-		return false;
-	}
-
-	abs_path = AbsoluteConfigLocation(base_dir, config_file, calling_file);
-
-	/* Reject direct recursion */
-	if (calling_file && strcmp(abs_path, calling_file) == 0)
-	{
-		item_list_append_format(error_list,
-								_("configuration file recursion in \"%s\""),
-								calling_file);
-		pfree(abs_path);
-		return false;
-	}
-
-	fp = fopen(abs_path, "r");
-	if (!fp)
-	{
-		if (strict == false)
-		{
-			item_list_append_format(error_list,
-									"skipping configuration file \"%s\"",
-									abs_path);
-		}
-		else
-		{
-			item_list_append_format(error_list,
-									"could not open configuration file \"%s\": %s",
-									abs_path,
-									strerror(errno));
-			success = false;
-		}
-	}
-	else
-	{
-		success = ProcessConfigFp(fp, abs_path, calling_file, depth + 1, base_dir, contents, error_list, warning_list);
-	}
-
-	free(abs_path);
-
-	return success;
-}
-
-static bool
-ProcessConfigFp(FILE *fp, const char *config_file, const char *calling_file, int depth, const char *base_dir, KeyValueList *contents, ItemList *error_list, ItemList *warning_list)
-{
-	volatile bool OK = true;
-	volatile YY_BUFFER_STATE lex_buffer = NULL;
-	sigjmp_buf	flex_fatal_jmp;
-	int			errorcount;
-	int			token;
-
-	if (sigsetjmp(flex_fatal_jmp, 1) == 0)
-	{
-		CONF_flex_fatal_jmp = &flex_fatal_jmp;
-	}
-	else
-	{
-		/*
-		 * Regain control after a fatal, internal flex error.  It may have
-		 * corrupted parser state.  Consequently, abandon the file, but trust
-		 * that the state remains sane enough for yy_delete_buffer().
-		 */
-		item_list_append_format(error_list,
-								"%s at file \"%s\" line %u",
-								CONF_flex_fatal_errmsg, config_file, ConfigFileLineno);
-		OK = false;
-		goto cleanup;
-	}
-
-	/*
-	 * Parse
-	 */
-	ConfigFileLineno = 1;
-	errorcount = 0;
-
-	lex_buffer = yy_create_buffer(fp, YY_BUF_SIZE);
-	yy_switch_to_buffer(lex_buffer);
-
-	/* This loop iterates once per logical line */
-	while ((token = yylex()))
-	{
-		char	   *opt_name = NULL;
-		char	   *opt_value = NULL;
-
-		if (token == CONF_EOL)	/* empty or comment line */
-			continue;
-
-		/* first token on line is option name */
-		if (token != CONF_ID && token != CONF_QUALIFIED_ID)
-			goto parse_error;
-		opt_name = pstrdup(yytext);
-
-		/* next we have an optional equal sign; discard if present */
-		token = yylex();
-		if (token == CONF_EQUALS)
-			token = yylex();
-
-		/* now we must have the option value */
-		if (token != CONF_ID &&
-			token != CONF_STRING &&
-			token != CONF_INTEGER &&
-			token != CONF_REAL &&
-			token != CONF_UNQUOTED_STRING)
-			goto parse_error;
-		if (token == CONF_STRING)	/* strip quotes and escapes */
-			opt_value = CONF_scanstr(yytext);
-		else
-			opt_value = pstrdup(yytext);
-
-		/* now we'd like an end of line, or possibly EOF */
-		token = yylex();
-		if (token != CONF_EOL)
-		{
-			if (token != 0)
-				goto parse_error;
-			/* treat EOF like \n for line numbering purposes, cf bug 4752 */
-			ConfigFileLineno++;
-		}
-
-		/* Handle include files */
-		if (base_dir != NULL && strcasecmp(opt_name, "include_dir") == 0)
-		{
-			/*
-			 * An include_dir directive isn't a variable and should be
-			 * processed immediately.
-			 */
-			if (!ProcessConfigDirectory(base_dir, opt_value, config_file,
-										depth + 1, contents,
-									    error_list, warning_list))
-				OK = false;
-			yy_switch_to_buffer(lex_buffer);
-			pfree(opt_name);
-			pfree(opt_value);
-		}
-		else if (base_dir != NULL && strcasecmp(opt_name, "include_if_exists") == 0)
-		{
-			if (!ProcessConfigFile(base_dir, opt_value, config_file,
-								   false, depth + 1, contents,
-								   error_list, warning_list))
-				OK = false;
-
-			yy_switch_to_buffer(lex_buffer);
-			pfree(opt_name);
-			pfree(opt_value);
-		}
-		else if (base_dir != NULL && strcasecmp(opt_name, "include") == 0)
-		{
-			if (!ProcessConfigFile(base_dir, opt_value, config_file,
-								   true, depth + 1, contents,
-								   error_list, warning_list))
-				OK = false;
-
-			yy_switch_to_buffer(lex_buffer);
-			pfree(opt_name);
-			pfree(opt_value);
-		}
-		else
-		{
-			/* OK, process the option name and value */
-			if (contents != NULL)
-			{
-				key_value_list_replace_or_set(contents,
-											  opt_name,
-											  opt_value);
-			}
-			else
-			{
-				parse_configuration_item(error_list,
-										 warning_list,
-										 opt_name,
-										 opt_value);
-			}
-
-		}
-
-
-		/* break out of loop if read EOF, else loop for next line */
-		if (token == 0)
-			break;
-		continue;
-
-parse_error:
-		/* release storage if we allocated any on this line */
-		if (opt_name)
-			pfree(opt_name);
-		if (opt_value)
-			pfree(opt_value);
-
-		/* report the error */
-		if (token == CONF_EOL || token == 0)
-		{
-			item_list_append_format(error_list,
-									_("syntax error in file \"%s\" line %u, near end of line"),
-								    config_file, ConfigFileLineno - 1);
-		}
-		else
-		{
-			item_list_append_format(error_list,
-									_("syntax error in file \"%s\" line %u, near token \"%s\""),
-									config_file, ConfigFileLineno, yytext);
-		}
-		OK = false;
-		errorcount++;
-
-		/*
-		 * To avoid producing too much noise when fed a totally bogus file,
-		 * give up after 100 syntax errors per file (an arbitrary number).
-		 * Also, if we're only logging the errors at DEBUG level anyway, might
-		 * as well give up immediately.  (This prevents postmaster children
-		 * from bloating the logs with duplicate complaints.)
-		 */
-		if (errorcount >= 100)
-		{
-			fprintf(stderr,
- 				   _("too many syntax errors found, abandoning file \"%s\"\n"),
-				   config_file);
-			break;
-		}
-
-		/* resync to next end-of-line or EOF */
-		while (token != CONF_EOL && token != 0)
-			token = yylex();
-		/* break out of loop on EOF */
-		if (token == 0)
-			break;
-	}
-
-cleanup:
-	yy_delete_buffer(lex_buffer);
-
-	return OK;
-}
-
-/*
- * Read and parse all config files in a subdirectory in alphabetical order
- *
- * includedir is the absolute or relative path to the subdirectory to scan.
- *
- * See ProcessConfigFp for further details.
- */
-static bool
-ProcessConfigDirectory(const char *base_dir, const char *includedir, const char *calling_file, int depth, KeyValueList *contents, ItemList *error_list, ItemList *warning_list)
-{
-	char	   *directory;
-	DIR		   *d;
-	struct dirent *de;
-	char	  **filenames;
-	int			num_filenames;
-	int			size_filenames;
-	bool		status;
-
-	/*
-	 * Reject directory name that is all-blank (including empty), as that
-	 * leads to confusion --- we'd read the containing directory, typically
-	 * resulting in recursive inclusion of the same file(s).
-	 */
-	if (strspn(includedir, " \t\r\n") == strlen(includedir))
-	{
-		item_list_append_format(error_list,
-								_("empty configuration directory name: \"%s\""),
-								includedir);
-
-		return false;
-	}
-
-	directory = AbsoluteConfigLocation(base_dir, includedir, calling_file);
-	d = opendir(directory);
-	if (d == NULL)
-	{
-		item_list_append_format(error_list,
-								_("could not open configuration directory \"%s\": %s"),
-								directory,
-								strerror(errno));
-		status = false;
-		goto cleanup;
-	}
-
-	/*
-	 * Read the directory and put the filenames in an array, so we can sort
-	 * them prior to processing the contents.
-	 */
-	size_filenames = 32;
-	filenames = (char **) palloc(size_filenames * sizeof(char *));
-	num_filenames = 0;
-
-	while ((de = readdir(d)) != NULL)
-	{
-		struct stat st;
-		char		filename[MAXPGPATH];
-
-		/*
-		 * Only parse files with names ending in ".conf".  Explicitly reject
-		 * files starting with ".".  This excludes things like "." and "..",
-		 * as well as typical hidden files, backup files, and editor debris.
-		 */
-		if (strlen(de->d_name) < 6)
-			continue;
-		if (de->d_name[0] == '.')
-			continue;
-		if (strcmp(de->d_name + strlen(de->d_name) - 5, ".conf") != 0)
-			continue;
-
-		join_path_components(filename, directory, de->d_name);
-		canonicalize_path(filename);
-		if (stat(filename, &st) == 0)
-		{
-			if (!S_ISDIR(st.st_mode))
-			{
-				/* Add file to array, increasing its size in blocks of 32 */
-				if (num_filenames >= size_filenames)
-				{
-					size_filenames += 32;
-					filenames = (char **) repalloc(filenames,
-											size_filenames * sizeof(char *));
-				}
-				filenames[num_filenames] = pstrdup(filename);
-				num_filenames++;
-			}
-		}
-		else
-		{
-			/*
-			 * stat does not care about permissions, so the most likely reason
-			 * a file can't be accessed now is if it was removed between the
-			 * directory listing and now.
-			 */
-			item_list_append_format(error_list,
-									_("could not stat file \"%s\": %s"),
-									filename, strerror(errno));
-			status = false;
-			goto cleanup;
-		}
-	}
-
-	if (num_filenames > 0)
-	{
-		int			i;
-
-		qsort(filenames, num_filenames, sizeof(char *), pg_qsort_strcmp);
-		for (i = 0; i < num_filenames; i++)
-		{
-			if (!ProcessConfigFile(base_dir, filenames[i], calling_file,
-								   true, depth, contents,
-								   error_list, warning_list))
-			{
-				status = false;
-				goto cleanup;
-			}
-		}
-	}
-	status = true;
-
-
-cleanup:
-	if (d)
-		closedir(d);
-	pfree(directory);
-	return status;
-}
-
-/*
- *		scanstr
- *
- * Strip the quotes surrounding the given string, and collapse any embedded
- * '' sequences and backslash escapes.
- *
- * the string returned is palloc'd and should eventually be pfree'd by the
- * caller.
- */
-static char *
-CONF_scanstr(const char *s)
-{
-	char	   *newStr;
-	int			len,
-				i,
-				j;
-
-	Assert(s != NULL && s[0] == '\'');
-	len = strlen(s);
-	Assert(s != NULL);
-
-	Assert(len >= 2);
-	Assert(s[len - 1] == '\'');
-
-	/* Skip the leading quote; we'll handle the trailing quote below */
-	s++, len--;
-
-	/* Since len still includes trailing quote, this is enough space */
-	newStr = palloc(len);
-
-	for (i = 0, j = 0; i < len; i++)
-	{
-		if (s[i] == '\\')
-		{
-			i++;
-			switch (s[i])
-			{
-				case 'b':
-					newStr[j] = '\b';
-					break;
-				case 'f':
-					newStr[j] = '\f';
-					break;
-				case 'n':
-					newStr[j] = '\n';
-					break;
-				case 'r':
-					newStr[j] = '\r';
-					break;
-				case 't':
-					newStr[j] = '\t';
-					break;
-				case '0':
-				case '1':
-				case '2':
-				case '3':
-				case '4':
-				case '5':
-				case '6':
-				case '7':
-					{
-						int			k;
-						long		octVal = 0;
-
-						for (k = 0;
-							 s[i + k] >= '0' && s[i + k] <= '7' && k < 3;
-							 k++)
-							octVal = (octVal << 3) + (s[i + k] - '0');
-						i += k - 1;
-						newStr[j] = ((char) octVal);
-					}
-					break;
-				default:
-					newStr[j] = s[i];
-					break;
-			}					/* switch */
-		}
-		else if (s[i] == '\'' && s[i + 1] == '\'')
-		{
-			/* doubled quote becomes just one quote */
-			newStr[j] = s[++i];
-		}
-		else
-			newStr[j] = s[i];
-		j++;
-	}
-
-	/* We copied the ending quote to newStr, so replace with \0 */
-	Assert(j > 0 && j <= len);
-	newStr[--j] = '\0';
-
-	return newStr;
-}
-
-/*
- * Given a configuration file or directory location that may be a relative
- * path, return an absolute one.  We consider the location to be relative to
- * the directory holding the calling file, or to DataDir if no calling file.
- */
-static char *
-AbsoluteConfigLocation(const char *base_dir, const char *location, const char *calling_file)
-{
-	char		abs_path[MAXPGPATH];
-
-	if (is_absolute_path(location))
-		return strdup(location);
-
-    if (calling_file != NULL)
-	{
-		strlcpy(abs_path, calling_file, sizeof(abs_path));
-		get_parent_directory(abs_path);
-		join_path_components(abs_path, abs_path, location);
-		canonicalize_path(abs_path);
-	}
-	else if (base_dir != NULL)
-	{
-		join_path_components(abs_path, base_dir, location);
-		canonicalize_path(abs_path);
-	}
-	else
-	{
-		strlcpy(abs_path, location, sizeof(abs_path));
-	}
-
-	return strdup(abs_path);
-}
-
-
-/*
- * Flex fatal errors bring us here.  Stash the error message and jump back to
- * ParseConfigFp().  Assume all msg arguments point to string constants; this
- * holds for flex 2.5.31 (earliest we support) and flex 2.5.35 (latest as of
- * this writing).  Otherwise, we would need to copy the message.
- *
- * We return "int" since this takes the place of calls to fprintf().
-*/
-static int
-CONF_flex_fatal(const char *msg)
-{
-	CONF_flex_fatal_errmsg = msg;
-	siglongjmp(*CONF_flex_fatal_jmp, 1);
-	return 0;					/* keep compiler quiet */
-}

configfile.h

@@ -1,7 +1,7 @@
 /*
  * configfile.h
  *
- * Copyright (c) EnterpriseDB Corporation, 2010-2021
+ * Copyright (c) 2ndQuadrant, 2010-2017
  *
  *
  * This program is free software: you can redistribute it and/or modify
@@ -28,12 +28,6 @@
 /* magic number for use in t_recovery_conf */
 #define TARGET_TIMELINE_LATEST 0
 
-/*
- * This is defined in src/include/utils.h, however it's not practical
- * to include that from a frontend application.
- */
-#define PG_AUTOCONF_FILENAME "postgresql.auto.conf"
-
 extern bool config_file_found;
 extern char config_file_path[MAXPGPATH];
 
@@ -43,18 +37,6 @@ typedef enum
 	FAILOVER_AUTOMATIC
 } failover_mode_opt;
 
-typedef enum
-{
-	CHECK_PING,
-	CHECK_QUERY,
-	CHECK_CONNECTION
-} ConnectionCheckType;
-
-typedef enum
-{
-	REPLICATION_TYPE_PHYSICAL
-} ReplicationType;
-
 typedef struct EventNotificationListCell
 {
 	struct EventNotificationListCell *next;
@@ -83,108 +65,31 @@ typedef struct TablespaceList
 } TablespaceList;
 
 
-typedef enum
-{
-	CONFIG_BOOL,
-	CONFIG_INT,
-	CONFIG_STRING,
-	CONFIG_FAILOVER_MODE,
-	CONFIG_CONNECTION_CHECK_TYPE,
-	CONFIG_EVENT_NOTIFICATION_LIST,
-	CONFIG_TABLESPACE_MAPPING,
-    CONFIG_REPLICATION_TYPE
-} ConfigItemType;
-
-
-typedef struct ConfigFileSetting
-{
-	const char	   *name;
-	ConfigItemType  type;
-    union
-    {
-        int		   *intptr;
-        char	   *strptr;
-		bool	   *boolptr;
-		failover_mode_opt *failovermodeptr;
-		ConnectionCheckType *checktypeptr;
-		EventNotificationList *notificationlistptr;
-		TablespaceList *tablespacemappingptr;
-		ReplicationType *replicationtypeptr;
-	} val;
-	union {
-		int			intdefault;
-		const char *strdefault;
-		bool		booldefault;
-		failover_mode_opt failovermodedefault;
-		ConnectionCheckType checktypedefault;
-		ReplicationType replicationtypedefault;
-	} defval;
-	union {
-		int				intminval;
-	} minval;
-	union {
-		int				strmaxlen;
-	} maxval;
-	struct {
-		void (*process_func)(const char *, const char *, char *, ItemList *errors);
-		void (*postprocess_func)(const char *, const char *, char *, ItemList *errors);
-		bool	   *providedptr;
-	} process;
-} ConfigFileSetting;
-
-/* Declare the main configfile structure for client applications */
-extern ConfigFileSetting config_file_settings[];
-
 typedef struct
 {
 	/* node information */
 	int			node_id;
-	char		node_name[NAMEDATALEN];
+	char		node_name[MAXLEN];
 	char		conninfo[MAXLEN];
 	char		replication_user[NAMEDATALEN];
 	char		data_directory[MAXPGPATH];
-	char		config_directory[MAXPGPATH];
 	char		pg_bindir[MAXPGPATH];
-	char		repmgr_bindir[MAXPGPATH];
+	int			replication_type;
-	ReplicationType	replication_type;
 
 	/* log settings */
 	char		log_level[MAXLEN];
 	char		log_facility[MAXLEN];
-	char		log_file[MAXPGPATH];
+	char		log_file[MAXLEN];
 	int			log_status_interval;
 
-	/* standby clone settings */
+	/* standby action settings */
 	bool		use_replication_slots;
 	char		pg_basebackup_options[MAXLEN];
 	char		restore_command[MAXLEN];
 	TablespaceList tablespace_mapping;
 	char		recovery_min_apply_delay[MAXLEN];
 	bool		recovery_min_apply_delay_provided;
-	char		archive_cleanup_command[MAXLEN];
 	bool		use_primary_conninfo_password;
-	char		passfile[MAXPGPATH];
-	char		pg_backupapi_backup_id[NAMEDATALEN];
-	char		pg_backupapi_host[NAMEDATALEN];
-	char		pg_backupapi_node_name[NAMEDATALEN];
-	char		pg_backupapi_remote_ssh_command[MAXLEN];
-
-	/* standby promote settings */
-	int			promote_check_timeout;
-	int			promote_check_interval;
-
-	/* standby follow settings */
-	int			primary_follow_timeout;
-	int			standby_follow_timeout;
-	bool		standby_follow_restart;
-
-	/* standby switchover settings */
-	int			shutdown_check_timeout;
-	int			standby_reconnect_timeout;
-	int			wal_receive_check_timeout;
-
-	/* node rejoin settings */
-	int			node_rejoin_timeout;
 
 	/* node check settings */
 	int			archive_ready_warning;
@@ -192,9 +97,6 @@ typedef struct
 	int			replication_lag_warning;
 	int			replication_lag_critical;
 
-	/* witness settings */
-	int			witness_sync_interval;
-
 	/* repmgrd settings */
 	failover_mode_opt failover;
 	char		location[MAXLEN];
@@ -208,37 +110,22 @@ typedef struct
 	int			degraded_monitoring_timeout;
 	int			async_query_timeout;
 	int			primary_notification_timeout;
-	int			repmgrd_standby_startup_timeout;
+	int			primary_follow_timeout;
-	char		repmgrd_pid_file[MAXPGPATH];
+
-	bool		repmgrd_exit_on_inactive_node;
+	/* BDR settings */
-	bool		standby_disconnect_on_failover;
+	bool		bdr_local_monitoring_only;
-	int			sibling_nodes_disconnect_timeout;
+	bool		bdr_recovery_timeout;
-	ConnectionCheckType connection_check_type;
-	bool		primary_visibility_consensus;
-	bool		always_promote;
-	char		failover_validation_command[MAXPGPATH];
-	int			election_rerun_interval;
-	int			child_nodes_check_interval;
-	int			child_nodes_disconnect_min_count;
-	int			child_nodes_connected_min_count;
-	bool		child_nodes_connected_include_witness;
-	int			child_nodes_disconnect_timeout;
-	char		child_nodes_disconnect_command[MAXPGPATH];
 
 	/* service settings */
 	char		pg_ctl_options[MAXLEN];
-	char		service_start_command[MAXPGPATH];
+	char		service_stop_command[MAXLEN];
-	char		service_stop_command[MAXPGPATH];
+	char		service_start_command[MAXLEN];
-	char		service_restart_command[MAXPGPATH];
+	char		service_restart_command[MAXLEN];
-	char		service_reload_command[MAXPGPATH];
+	char		service_reload_command[MAXLEN];
-	char		service_promote_command[MAXPGPATH];
+	char		service_promote_command[MAXLEN];
-
-	/* repmgrd service settings */
-	char		repmgrd_service_start_command[MAXPGPATH];
-	char		repmgrd_service_stop_command[MAXPGPATH];
 
 	/* event notification settings */
-	char		event_notification_command[MAXPGPATH];
+	char		event_notification_command[MAXLEN];
 	char		event_notifications_orig[MAXLEN];
 	EventNotificationList event_notifications;
 
@@ -251,35 +138,58 @@ typedef struct
 	char		rsync_options[MAXLEN];
 	char		ssh_options[MAXLEN];
 
-	/*
+	/* undocumented test settings */
-	 * undocumented settings
-	 *
-	 * These settings are for testing or experimental features
-	 * and may be changed without notice.
-	 */
-
-	/* experimental settings */
-	bool		reconnect_loop_sync;
-
-	/* test settings */
 	int			promote_delay;
-	int			failover_delay;
-	char		connection_check_query[MAXLEN];
 } t_configuration_options;
 
+/*
+ * The following will initialize the structure with a minimal set of options;
+ * actual defaults are set in parse_config() before parsing the configuration file
+ */
+
+#define T_CONFIGURATION_OPTIONS_INITIALIZER { \
+		/* node information */ \
+		UNKNOWN_NODE_ID, "", "", "", "", "", REPLICATION_TYPE_PHYSICAL,	\
+		/* log settings */ \
+		"", "", "", DEFAULT_LOG_STATUS_INTERVAL,	\
+		/* standby action settings */ \
+		false, "", "", { NULL, NULL }, "", false, false, \
+		/* node check settings */ \
+		DEFAULT_ARCHIVE_READY_WARNING, DEFAULT_ARCHIVE_READY_CRITICAL, \
+		DEFAULT_REPLICATION_LAG_WARNING, DEFAULT_REPLICATION_LAG_CRITICAL, \
+		/* repmgrd settings */ \
+		FAILOVER_MANUAL, DEFAULT_LOCATION, DEFAULT_PRIORITY, "", "", \
+		DEFAULT_MONITORING_INTERVAL, \
+		DEFAULT_RECONNECTION_ATTEMPTS, \
+        DEFAULT_RECONNECTION_INTERVAL, \
+        false, -1, \
+		DEFAULT_ASYNC_QUERY_TIMEOUT, \
+		DEFAULT_PRIMARY_NOTIFICATION_TIMEOUT,	\
+		DEFAULT_PRIMARY_FOLLOW_TIMEOUT,	\
+		/* BDR settings */ \
+		false, DEFAULT_BDR_RECOVERY_TIMEOUT, \
+		/* service settings */ \
+		"", "", "", "", "", "", \
+		/* event notification settings */ \
+		"", "", { NULL, NULL }, \
+		/* barman settings */ \
+		"", "", "",	 \
+		/* rsync/ssh settings */ \
+		 "", "", \
+		/* undocumented test settings */ \
+		0 \
+ }
+
 
-/* Declare the main configfile structure for client applications */
-extern t_configuration_options config_file_options;
 
 typedef struct
 {
 	char		slot[MAXLEN];
-	char		wal_method[MAXLEN];
+	char		xlog_method[MAXLEN];
-	char		waldir[MAXPGPATH];
 	bool		no_slot;		/* from PostgreSQL 10 */
 } t_basebackup_options;
 
-#define T_BASEBACKUP_OPTIONS_INITIALIZER { "", "", "", false }
+#define T_BASEBACKUP_OPTIONS_INITIALIZER { "", "", false }
 
 
 typedef enum
@@ -331,53 +241,30 @@ typedef struct
 	"", "", "", "" \
 }
 
-#include "dbutils.h"
+
 
 void		set_progname(const char *argv0);
 const char *progname(void);
 
-void		load_config(const char *config_file, bool verbose, bool terse, char *argv0);
+void		load_config(const char *config_file, bool verbose, bool terse, t_configuration_options *options, char *argv0);
-bool		reload_config(t_server_type server_type);
+void		parse_config(t_configuration_options *options, bool terse);
-void		dump_config(void);
+bool		reload_config(t_configuration_options *orig_options);
-
-void		parse_configuration_item(ItemList *error_list, ItemList *warning_list, const char *name, const char *value);
 
 bool		parse_recovery_conf(const char *data_dir, t_recovery_conf *conf);
 
-bool		parse_bool(const char *s,
-					   const char *config_item,
-					   ItemList *error_list);
-
 int repmgr_atoi(const char *s,
 			const char *config_item,
 			ItemList *error_list,
 			int minval);
 
-void parse_time_unit_parameter(const char *name, const char *value, char *dest, ItemList *errors);
-void repmgr_canonicalize_path(const char *name, const char *value, char *config_item, ItemList *errors);
 
 bool parse_pg_basebackup_options(const char *pg_basebackup_options,
 							t_basebackup_options *backup_options,
 							int server_version_num,
 							ItemList *error_list);
 
-int parse_output_to_argv(const char *string, char ***argv_array);
-void free_parsed_argv(char ***argv_array);
-const char *format_failover_mode(failover_mode_opt failover);
-
 /* called by repmgr-client and repmgrd */
-void		exit_with_cli_errors(ItemList *error_list, const char *repmgr_command);
+void		exit_with_cli_errors(ItemList *error_list);
-
 void		print_item_list(ItemList *item_list);
-const char *print_replication_type(ReplicationType type);
-const char *print_connection_check_type(ConnectionCheckType type);
-char 	   *print_event_notification_list(EventNotificationList *list);
-char 	   *print_tablespace_mapping(TablespaceList *tablespacemappingptr);
-
-extern bool modify_auto_conf(const char *data_dir, KeyValueList *items);
-
-extern bool ProcessRepmgrConfigFile(const char *config_file, const char *base_dir, ItemList *error_list, ItemList *warning_list);
-
-extern bool ProcessPostgresConfigFile(const char *config_file, const char *base_dir, bool strict, KeyValueList *contents, ItemList *error_list, ItemList *warning_list);
 
 #endif							/* _REPMGR_CONFIGFILE_H_ */

configure

@@ -1,8 +1,8 @@
 #! /bin/sh
 # Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.69 for repmgr 5.4.0.
+# Generated by GNU Autoconf 2.69 for repmgr 4.0beta1.
 #
-# Report bugs to <repmgr@googlegroups.com>.
+# Report bugs to <pgsql-bugs@postgresql.org>.
 #
 #
 # Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
@@ -11,7 +11,7 @@
 # This configure script is free software; the Free Software Foundation
 # gives unlimited permission to copy, distribute and modify it.
 #
-# Copyright (c) 2010-2021, EnterpriseDB Corporation
+# Copyright (c) 2010-2017, 2ndQuadrant Ltd.
 ## -------------------- ##
 ## M4sh Initialization. ##
 ## -------------------- ##
@@ -269,7 +269,7 @@ fi
     $as_echo "$0: be upgraded to zsh 4.3.4 or later."
   else
     $as_echo "$0: Please tell bug-autoconf@gnu.org and
-$0: repmgr@googlegroups.com about your system, including
+$0: pgsql-bugs@postgresql.org about your system, including
 $0: any error possibly output before this message. Then
 $0: install a modern shell, or manually run the script
 $0: under such a shell if you do have one."
@@ -582,16 +582,13 @@ MAKEFLAGS=
 # Identity of this package.
 PACKAGE_NAME='repmgr'
 PACKAGE_TARNAME='repmgr'
-PACKAGE_VERSION='5.4.0'
+PACKAGE_VERSION='4.0beta1'
-PACKAGE_STRING='repmgr 5.4.0'
+PACKAGE_STRING='repmgr 4.0beta1'
-PACKAGE_BUGREPORT='repmgr@googlegroups.com'
+PACKAGE_BUGREPORT='pgsql-bugs@postgresql.org'
-PACKAGE_URL='https://repmgr.org/'
+PACKAGE_URL='https://2ndquadrant.com/en/resources/repmgr/'
 
 ac_subst_vars='LTLIBOBJS
 LIBOBJS
-HAVE_SED
-HAVE_GSED
-HAVE_GNUSED
 vpath_build
 SED
 PG_CONFIG
@@ -636,6 +633,7 @@ SHELL'
 ac_subst_files=''
 ac_user_opts='
 enable_option_checking
+with_bdr_only
 '
       ac_precious_vars='build_alias
 host_alias
@@ -1181,7 +1179,7 @@ if test "$ac_init_help" = "long"; then
   # Omit some internal or obsolete options to make the list less imposing.
   # This message is too long to be a string in the A/UX 3.1 sh.
   cat <<_ACEOF
-\`configure' configures repmgr 5.4.0 to adapt to many kinds of systems.
+\`configure' configures repmgr 4.0beta1 to adapt to many kinds of systems.
 
 Usage: $0 [OPTION]... [VAR=VALUE]...
 
@@ -1242,18 +1240,23 @@ fi
 
 if test -n "$ac_init_help"; then
   case $ac_init_help in
-     short | recursive ) echo "Configuration of repmgr 5.4.0:";;
+     short | recursive ) echo "Configuration of repmgr 4.0beta1:";;
    esac
   cat <<\_ACEOF
 
+Optional Packages:
+  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
+  --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
+  --with-bdr-only         BDR-only build
+
 Some influential environment variables:
   PG_CONFIG   Location to find pg_config for target PostgreSQL (default PATH)
 
 Use these variables to override the choices made by `configure' or to help
 it to find libraries and programs with nonstandard names/locations.
 
-Report bugs to <repmgr@googlegroups.com>.
+Report bugs to <pgsql-bugs@postgresql.org>.
-repmgr home page: <https://repmgr.org/>.
+repmgr home page: <https://2ndquadrant.com/en/resources/repmgr/>.
 _ACEOF
 ac_status=$?
 fi
@@ -1316,14 +1319,14 @@ fi
 test -n "$ac_init_help" && exit $ac_status
 if $ac_init_version; then
   cat <<\_ACEOF
-repmgr configure 5.4.0
+repmgr configure 4.0beta1
 generated by GNU Autoconf 2.69
 
 Copyright (C) 2012 Free Software Foundation, Inc.
 This configure script is free software; the Free Software Foundation
 gives unlimited permission to copy, distribute and modify it.
 
-Copyright (c) 2010-2021, EnterpriseDB Corporation
+Copyright (c) 2010-2017, 2ndQuadrant Ltd.
 _ACEOF
   exit
 fi
@@ -1335,7 +1338,7 @@ cat >config.log <<_ACEOF
 This file contains any messages produced by compilers while
 running configure, to aid debugging if configure makes a mistake.
 
-It was created by repmgr $as_me 5.4.0, which was
+It was created by repmgr $as_me 4.0beta1, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   $ $0 $@
@@ -1691,6 +1694,20 @@ ac_config_headers="$ac_config_headers config.h"
 
 
 
+
+# Check whether --with-bdr_only was given.
+if test "${with_bdr_only+set}" = set; then :
+  withval=$with_bdr_only;
+fi
+
+if test "x$with_bdr_only" != "x"; then :
+
+$as_echo "#define BDR_ONLY \"1\"" >>confdefs.h
+
+
+fi
+
+
 { $as_echo "$as_me:${as_lineno-$LINENO}: checking for a sed that does not truncate output" >&5
 $as_echo_n "checking for a sed that does not truncate output... " >&6; }
 if ${ac_cv_path_SED+:} false; then :
@@ -1811,11 +1828,11 @@ fi
 pgac_pg_config_version=$($PG_CONFIG --version 2>/dev/null)
 
 major_version_num=$(echo "$pgac_pg_config_version"|
-              $SED -e 's/^[^0-9]\+ \([0-9]\{1,2\}\).*$/\1/')
+              $SED -e 's/^PostgreSQL \([0-9]\{1,2\}\).*$/\1/')
 
 if test "$major_version_num" -lt '10'; then
     version_num=$(echo "$pgac_pg_config_version"|
-                $SED -e 's/^[^0-9]\+ \([0-9]*\)\.\([0-9]*\)\([a-zA-Z0-9.]*\)$/\1.\2/')
+                $SED -e 's/^PostgreSQL \([0-9]*\)\.\([0-9]*\)\([a-zA-Z0-9.]*\)$/\1.\2/')
 
     if test -z "$version_num"; then
         as_fn_error $? "could not detect the PostgreSQL version, wrong or broken pg_config?" "$LINENO" 5
@@ -1824,12 +1841,12 @@ if test "$major_version_num" -lt '10'; then
     version_num_int=$(echo "$version_num"|
                     $SED -e 's/^\([0-9]*\)\.\([0-9]*\)$/\1\2/')
 
-    if test "$version_num_int" -lt '94'; then
+    if test "$version_num_int" -lt '93'; then
         as_fn_error $? "repmgr is not compatible with detected PostgreSQL version: $version_num" "$LINENO" 5
     fi
 else
     version_num=$(echo "$pgac_pg_config_version"|
-                $SED -e 's/^[^0-9]\+ \(.\+\)$/\1/')
+                $SED -e 's/^PostgreSQL \(.\+\)$/\1/')
 
     if test -z "$version_num"; then
         as_fn_error $? "could not detect the PostgreSQL version, wrong or broken pg_config?" "$LINENO" 5
@@ -1850,133 +1867,6 @@ else
 fi
 
 
-# Extract the first word of "gnused", so it can be a program name with args.
-set dummy gnused; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if ${ac_cv_prog_HAVE_GNUSED+:} false; then :
-  $as_echo_n "(cached) " >&6
-else
-  if test -n "$HAVE_GNUSED"; then
-  ac_cv_prog_HAVE_GNUSED="$HAVE_GNUSED" # Let the user override the test.
-else
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
-  IFS=$as_save_IFS
-  test -z "$as_dir" && as_dir=.
-    for ac_exec_ext in '' $ac_executable_extensions; do
-  if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
-    ac_cv_prog_HAVE_GNUSED="yes"
-    $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
-    break 2
-  fi
-done
-  done
-IFS=$as_save_IFS
-
-  test -z "$ac_cv_prog_HAVE_GNUSED" && ac_cv_prog_HAVE_GNUSED="no"
-fi
-fi
-HAVE_GNUSED=$ac_cv_prog_HAVE_GNUSED
-if test -n "$HAVE_GNUSED"; then
-  { $as_echo "$as_me:${as_lineno-$LINENO}: result: $HAVE_GNUSED" >&5
-$as_echo "$HAVE_GNUSED" >&6; }
-else
-  { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
-# Extract the first word of "gsed", so it can be a program name with args.
-set dummy gsed; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if ${ac_cv_prog_HAVE_GSED+:} false; then :
-  $as_echo_n "(cached) " >&6
-else
-  if test -n "$HAVE_GSED"; then
-  ac_cv_prog_HAVE_GSED="$HAVE_GSED" # Let the user override the test.
-else
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
-  IFS=$as_save_IFS
-  test -z "$as_dir" && as_dir=.
-    for ac_exec_ext in '' $ac_executable_extensions; do
-  if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
-    ac_cv_prog_HAVE_GSED="yes"
-    $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
-    break 2
-  fi
-done
-  done
-IFS=$as_save_IFS
-
-  test -z "$ac_cv_prog_HAVE_GSED" && ac_cv_prog_HAVE_GSED="no"
-fi
-fi
-HAVE_GSED=$ac_cv_prog_HAVE_GSED
-if test -n "$HAVE_GSED"; then
-  { $as_echo "$as_me:${as_lineno-$LINENO}: result: $HAVE_GSED" >&5
-$as_echo "$HAVE_GSED" >&6; }
-else
-  { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
-# Extract the first word of "sed", so it can be a program name with args.
-set dummy sed; ac_word=$2
-{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
-$as_echo_n "checking for $ac_word... " >&6; }
-if ${ac_cv_prog_HAVE_SED+:} false; then :
-  $as_echo_n "(cached) " >&6
-else
-  if test -n "$HAVE_SED"; then
-  ac_cv_prog_HAVE_SED="$HAVE_SED" # Let the user override the test.
-else
-as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
-for as_dir in $PATH
-do
-  IFS=$as_save_IFS
-  test -z "$as_dir" && as_dir=.
-    for ac_exec_ext in '' $ac_executable_extensions; do
-  if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
-    ac_cv_prog_HAVE_SED="yes"
-    $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
-    break 2
-  fi
-done
-  done
-IFS=$as_save_IFS
-
-  test -z "$ac_cv_prog_HAVE_SED" && ac_cv_prog_HAVE_SED="no"
-fi
-fi
-HAVE_SED=$ac_cv_prog_HAVE_SED
-if test -n "$HAVE_SED"; then
-  { $as_echo "$as_me:${as_lineno-$LINENO}: result: $HAVE_SED" >&5
-$as_echo "$HAVE_SED" >&6; }
-else
-  { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
-$as_echo "no" >&6; }
-fi
-
-
-
-if test "$HAVE_GNUSED" = yes; then
- SED=gnused
-else
- if test "$HAVE_GSED" = yes; then
-  SED=gsed
- else
-  SED=sed
- fi
-fi
-
-
-
 ac_config_files="$ac_config_files Makefile"
 
 ac_config_files="$ac_config_files Makefile.global"
@@ -2487,7 +2377,7 @@ cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
 # report actual input values of CONFIG_FILES etc. instead of their
 # values after options handling.
 ac_log="
-This file was extended by repmgr $as_me 5.4.0, which was
+This file was extended by repmgr $as_me 4.0beta1, which was
 generated by GNU Autoconf 2.69.  Invocation command line was
 
   CONFIG_FILES    = $CONFIG_FILES
@@ -2543,14 +2433,14 @@ $config_files
 Configuration headers:
 $config_headers
 
-Report bugs to <repmgr@googlegroups.com>.
+Report bugs to <pgsql-bugs@postgresql.org>.
-repmgr home page: <https://repmgr.org/>."
+repmgr home page: <https://2ndquadrant.com/en/resources/repmgr/>."
 
 _ACEOF
 cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
 ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
 ac_cs_version="\\
-repmgr config.status 5.4.0
+repmgr config.status 4.0beta1
 configured by $0, generated by GNU Autoconf 2.69,
   with options \\"\$ac_cs_config\\"
 

configure.in

@@ -1,11 +1,17 @@
-AC_INIT([repmgr], [5.5.0], [repmgr@googlegroups.com], [repmgr], [https://repmgr.org/])
+AC_INIT([repmgr], [4.0beta1], [pgsql-bugs@postgresql.org], [repmgr], [https://2ndquadrant.com/en/resources/repmgr/])
 
-AC_COPYRIGHT([Copyright (c) 2010-2024, EnterpriseDB Corporation])
+AC_COPYRIGHT([Copyright (c) 2010-2017, 2ndQuadrant Ltd.])
 
 AC_CONFIG_HEADER(config.h)
 
 AC_ARG_VAR([PG_CONFIG], [Location to find pg_config for target PostgreSQL (default PATH)])
 
+AC_ARG_WITH([bdr_only], [AS_HELP_STRING([--with-bdr-only], [BDR-only build])])
+AS_IF([test "x$with_bdr_only" != "x"],
+    [AC_DEFINE([BDR_ONLY], ["1"], [Only build repmgr for BDR])]
+)
+
+
 AC_PROG_SED
 
 if test -z "$PG_CONFIG"; then
@@ -19,11 +25,11 @@ fi
 pgac_pg_config_version=$($PG_CONFIG --version 2>/dev/null)
 
 major_version_num=$(echo "$pgac_pg_config_version"|
-              $SED -e 's/^[[^0-9]]\+ \([[0-9]]\{1,2\}\).*$/\1/')
+              $SED -e 's/^PostgreSQL \([[0-9]]\{1,2\}\).*$/\1/')
 
 if test "$major_version_num" -lt '10'; then
     version_num=$(echo "$pgac_pg_config_version"|
-                $SED -e 's/^[[^0-9]]\+ \([[0-9]]*\)\.\([[0-9]]*\)\([[a-zA-Z0-9.]]*\)$/\1.\2/')
+                $SED -e 's/^PostgreSQL \([[0-9]]*\)\.\([[0-9]]*\)\([[a-zA-Z0-9.]]*\)$/\1.\2/')
 
     if test -z "$version_num"; then
         AC_MSG_ERROR([could not detect the PostgreSQL version, wrong or broken pg_config?])
@@ -32,12 +38,12 @@ if test "$major_version_num" -lt '10'; then
     version_num_int=$(echo "$version_num"|
                     $SED -e 's/^\([[0-9]]*\)\.\([[0-9]]*\)$/\1\2/')
 
-    if test "$version_num_int" -lt '94'; then
+    if test "$version_num_int" -lt '93'; then
         AC_MSG_ERROR([repmgr is not compatible with detected PostgreSQL version: $version_num])
     fi
 else
     version_num=$(echo "$pgac_pg_config_version"|
-                $SED -e 's/^[[^0-9]]\+ \(.\+\)$/\1/')
+                $SED -e 's/^PostgreSQL \(.\+\)$/\1/')
 
     if test -z "$version_num"; then
         AC_MSG_ERROR([could not detect the PostgreSQL version, wrong or broken pg_config?])
@@ -57,42 +63,6 @@ else
 fi
 AC_SUBST(vpath_build)
 
-AC_CHECK_PROG(HAVE_GNUSED,gnused,yes,no)
-AC_CHECK_PROG(HAVE_GSED,gsed,yes,no)
-AC_CHECK_PROG(HAVE_SED,sed,yes,no)
-AC_CHECK_PROG(HAVE_FLEX,flex,yes,no)
-
-if test "$HAVE_GNUSED" = yes; then
- SED=gnused
-else
- if test "$HAVE_GSED" = yes; then
-  SED=gsed
- else
-  SED=sed
- fi
-fi
-AC_SUBST(SED)
-
-AS_IF([test x"$HAVE_FLEX" != x"yes"], AC_MSG_ERROR([flex should be installed first]))
-
-#Checking libraries
-GENERIC_LIB_FAILED_MSG="library should be installed"
-
-AC_CHECK_LIB(selinux, is_selinux_enabled, [],
-     [AC_MSG_ERROR(['selinux' $GENERIC_LIB_FAILED_MSG])])
-
-AC_CHECK_LIB(lz4, LZ4_compress_default, [],
-     [AC_MSG_ERROR(['Z4' $GENERIC_LIB_FAILED_MSG])])
-
-AC_CHECK_LIB(xslt, xsltCleanupGlobals, [],
-     [AC_MSG_ERROR(['xslt' $GENERIC_LIB_FAILED_MSG])])
-
-AC_CHECK_LIB(pam, pam_start, [],
-     [AC_MSG_ERROR(['pam' $GENERIC_LIB_FAILED_MSG])])
-
-AC_CHECK_LIB(gssapi_krb5, gss_init_sec_context, [],
-     [AC_MSG_ERROR([gssapi_krb5 $GENERIC_LIB_FAILED_MSG])])
-
 AC_CONFIG_FILES([Makefile])
 AC_CONFIG_FILES([Makefile.global])
 AC_OUTPUT

contrib/convert-config.pl

@@ -73,16 +73,7 @@ while(<$fh>) {
         if ($param eq 'data_directory') {
             $data_directory_found = 1;
         }
-
+        push @outp, $line;
-        # Don't quote numbers
-        if ($value =~ /^\d+$/) {
-            push @outp, sprintf(q|%s=%s|, $param, $value);
-        }
-        # Quote everything else
-        else {
-            $value =~ s/'/''/g;
-            push @outp, sprintf(q|%s='%s'|, $param, $value);
-        }
     }
 }
 
@@ -92,6 +83,6 @@ print join("\n", @outp);
 print "\n";
 
 if ($data_directory_found == 0) {
-    print "data_directory=''\n";
+    print "data_directory=\n";
 }
 

controldata.c

@@ -1,12 +1,6 @@
 /*
- * controldata.c - functions for reading the pg_control file
+ * controldata.c
- *
+ * Copyright (c) 2ndQuadrant, 2010-2017
- * The functions provided here enable repmgr to read a pg_control file
- * in a version-independent way, even if the PostgreSQL instance is not
- * running. For that reason we can't use on the pg_control_*() functions
- * provided in PostgreSQL 9.6 and later.
- *
- * Copyright (c) EnterpriseDB Corporation, 2010-2021
  *
  * Portions Copyright (c) 1996-2016, PostgreSQL Global Development Group
  * Portions Copyright (c) 1994, Regents of the University of California
@@ -36,53 +30,6 @@
 
 static ControlFileInfo *get_controlfile(const char *DataDir);
 
-int
-get_pg_version(const char *data_directory, char *version_string)
-{
-	char		PgVersionPath[MAXPGPATH] = "";
-	FILE	   *fp = NULL;
-	char	   *endptr = NULL;
-	char		file_version_string[MAX_VERSION_STRING] = "";
-	long		file_major, file_minor;
-	int			ret;
-
-	snprintf(PgVersionPath, MAXPGPATH, "%s/PG_VERSION", data_directory);
-
-	fp = fopen(PgVersionPath, "r");
-
-	if (fp == NULL)
-	{
-		log_warning(_("could not open file \"%s\" for reading"),
-					PgVersionPath);
-		log_detail("%s", strerror(errno));
-		return UNKNOWN_SERVER_VERSION_NUM;
-	}
-
-	file_version_string[0] = '\0';
-
-	ret = fscanf(fp, "%23s", file_version_string);
-	fclose(fp);
-
-	if (ret != 1 || endptr == file_version_string)
-	{
-		log_warning(_("unable to determine major version number from PG_VERSION"));
-
-		return UNKNOWN_SERVER_VERSION_NUM;
-	}
-
-	file_major = strtol(file_version_string, &endptr, 10);
-	file_minor = 0;
-
-	if (*endptr == '.')
-		file_minor = strtol(endptr + 1, NULL, 10);
-
-	if (version_string != NULL)
-		strncpy(version_string, file_version_string, MAX_VERSION_STRING);
-
-	return ((int) file_major * 10000) + ((int) file_minor * 100);
-}
-
-
 uint64
 get_system_identifier(const char *data_directory)
 {
@@ -92,33 +39,38 @@ get_system_identifier(const char *data_directory)
 	control_file_info = get_controlfile(data_directory);
 
 	if (control_file_info->control_file_processed == true)
-		system_identifier = control_file_info->system_identifier;
+		system_identifier = control_file_info->control_file->system_identifier;
+	else
+		system_identifier = UNKNOWN_SYSTEM_IDENTIFIER;
 
+	pfree(control_file_info->control_file);
 	pfree(control_file_info);
 
 	return system_identifier;
 }
 
-
+DBState
-bool
+get_db_state(const char *data_directory)
-get_db_state(const char *data_directory, DBState *state)
 {
 	ControlFileInfo *control_file_info = NULL;
-	bool control_file_processed;
+	DBState		state;
 
 	control_file_info = get_controlfile(data_directory);
-	control_file_processed = control_file_info->control_file_processed;
 
-	if (control_file_processed == true)
+	if (control_file_info->control_file_processed == true)
-		*state = control_file_info->state;
+		state = control_file_info->control_file->state;
+	else
+		/* if we were unable to parse the control file, assume DB is shut down */
+		state = DB_SHUTDOWNED;
 
+	pfree(control_file_info->control_file);
 	pfree(control_file_info);
 
-	return control_file_processed;
+	return state;
 }
 
 
-XLogRecPtr
+extern XLogRecPtr
 get_latest_checkpoint_location(const char *data_directory)
 {
 	ControlFileInfo *control_file_info = NULL;
@@ -126,9 +78,12 @@ get_latest_checkpoint_location(const char *data_directory)
 
 	control_file_info = get_controlfile(data_directory);
 
-	if (control_file_info->control_file_processed == true)
+	if (control_file_info->control_file_processed == false)
-		checkPoint = control_file_info->checkPoint;
+		return InvalidXLogRecPtr;
 
+	checkPoint = control_file_info->control_file->checkPoint;
+
+	pfree(control_file_info->control_file);
 	pfree(control_file_info);
 
 	return checkPoint;
@@ -139,13 +94,20 @@ int
 get_data_checksum_version(const char *data_directory)
 {
 	ControlFileInfo *control_file_info = NULL;
-	int			data_checksum_version = UNKNOWN_DATA_CHECKSUM_VERSION;
+	int			data_checksum_version = -1;
 
 	control_file_info = get_controlfile(data_directory);
 
-	if (control_file_info->control_file_processed == true)
+	if (control_file_info->control_file_processed == false)
-		data_checksum_version = (int) control_file_info->data_checksum_version;
+	{
+		data_checksum_version = -1;
+	}
+	else
+	{
+		data_checksum_version = (int) control_file_info->control_file->data_checksum_version;
+	}
 
+	pfree(control_file_info->control_file);
 	pfree(control_file_info);
 
 	return data_checksum_version;
@@ -172,148 +134,38 @@ describe_db_state(DBState state)
 		case DB_IN_PRODUCTION:
 			return _("in production");
 	}
-
 	return _("unrecognized status code");
 }
 
 
-TimeLineID
-get_timeline(const char *data_directory)
-{
-	ControlFileInfo *control_file_info = NULL;
-	TimeLineID		 timeline = -1;
-
-	control_file_info = get_controlfile(data_directory);
-
-	timeline = (int) control_file_info->timeline;
-
-	pfree(control_file_info);
-
-	return timeline;
-}
-
-
-TimeLineID
-get_min_recovery_end_timeline(const char *data_directory)
-{
-	ControlFileInfo *control_file_info = NULL;
-	TimeLineID		 timeline = -1;
-
-	control_file_info = get_controlfile(data_directory);
-
-	timeline = (int) control_file_info->minRecoveryPointTLI;
-
-	pfree(control_file_info);
-
-	return timeline;
-}
-
-
-XLogRecPtr
-get_min_recovery_location(const char *data_directory)
-{
-	ControlFileInfo *control_file_info = NULL;
-	XLogRecPtr	minRecoveryPoint  = InvalidXLogRecPtr;
-
-	control_file_info = get_controlfile(data_directory);
-
-	minRecoveryPoint = control_file_info->minRecoveryPoint;
-
-	pfree(control_file_info);
-
-	return minRecoveryPoint;
-}
-
-
 /*
- * We maintain our own version of get_controlfile() as we need cross-version
+ * we maintain our own version of get_controlfile() as we need cross-version
  * compatibility, and also don't care if the file isn't readable.
  */
 static ControlFileInfo *
 get_controlfile(const char *DataDir)
 {
-	char		file_version_string[MAX_VERSION_STRING] = "";
 	ControlFileInfo *control_file_info;
-	int			fd, version_num;
+	int			fd;
 	char		ControlFilePath[MAXPGPATH] = "";
-	void	   *ControlFileDataPtr = NULL;
-	int			expected_size = 0;
 
 	control_file_info = palloc0(sizeof(ControlFileInfo));
-
-	/* set default values */
 	control_file_info->control_file_processed = false;
-	control_file_info->system_identifier = UNKNOWN_SYSTEM_IDENTIFIER;
+	control_file_info->control_file = palloc0(sizeof(ControlFileData));
-	control_file_info->state = DB_SHUTDOWNED;
-	control_file_info->checkPoint = InvalidXLogRecPtr;
-	control_file_info->data_checksum_version = -1;
-	control_file_info->timeline = -1;
-	control_file_info->minRecoveryPointTLI = -1;
-	control_file_info->minRecoveryPoint = InvalidXLogRecPtr;
-
-	/*
-	 * Read PG_VERSION, as we'll need to determine which struct to read
-	 * the control file contents into
-	 */
-
-	version_num = get_pg_version(DataDir, file_version_string);
-
-	if (version_num == UNKNOWN_SERVER_VERSION_NUM)
-	{
-		log_warning(_("unable to determine server version number from PG_VERSION"));
-		return control_file_info;
-	}
-
-	if (version_num < MIN_SUPPORTED_VERSION_NUM)
-	{
-		log_warning(_("data directory appears to be initialised for %s"),
-					file_version_string);
-		log_detail(_("minimum supported PostgreSQL version is %s"),
-				   MIN_SUPPORTED_VERSION);
-		return control_file_info;
-	}
 
 	snprintf(ControlFilePath, MAXPGPATH, "%s/global/pg_control", DataDir);
 
 	if ((fd = open(ControlFilePath, O_RDONLY | PG_BINARY, 0)) == -1)
 	{
-		log_warning(_("could not open file \"%s\" for reading"),
+		log_debug("could not open file \"%s\" for reading: %s",
-					ControlFilePath);
+				  ControlFilePath, strerror(errno));
-		log_detail("%s", strerror(errno));
 		return control_file_info;
 	}
 
-	if (version_num >= 120000)
+	if (read(fd, control_file_info->control_file, sizeof(ControlFileData)) != sizeof(ControlFileData))
 	{
-#if PG_ACTUAL_VERSION_NUM >= 120000
+		log_debug("could not read file \"%s\": %s",
-		expected_size = sizeof(ControlFileData12);
+				  ControlFilePath, strerror(errno));
-		ControlFileDataPtr = palloc0(expected_size);
-#endif
-	}
-	else if (version_num >= 110000)
-	{
-		expected_size = sizeof(ControlFileData11);
-		ControlFileDataPtr = palloc0(expected_size);
-	}
-	else if (version_num >= 90500)
-	{
-		expected_size = sizeof(ControlFileData95);
-		ControlFileDataPtr = palloc0(expected_size);
-	}
-	else if (version_num >= 90400)
-	{
-		expected_size = sizeof(ControlFileData94);
-		ControlFileDataPtr = palloc0(expected_size);
-	}
-
-	if (read(fd, ControlFileDataPtr, expected_size) != expected_size)
-	{
-		log_warning(_("could not read file \"%s\""),
-					ControlFilePath);
-		log_detail("%s", strerror(errno));
-
-		close(fd);
-
 		return control_file_info;
 	}
 
@@ -321,62 +173,12 @@ get_controlfile(const char *DataDir)
 
 	control_file_info->control_file_processed = true;
 
-	if (version_num >= 120000)
-	{
-#if PG_ACTUAL_VERSION_NUM >= 120000
-		ControlFileData12 *ptr = (struct ControlFileData12 *)ControlFileDataPtr;
-		control_file_info->system_identifier = ptr->system_identifier;
-		control_file_info->state = ptr->state;
-		control_file_info->checkPoint = ptr->checkPoint;
-		control_file_info->data_checksum_version = ptr->data_checksum_version;
-		control_file_info->timeline = ptr->checkPointCopy.ThisTimeLineID;
-		control_file_info->minRecoveryPointTLI = ptr->minRecoveryPointTLI;
-		control_file_info->minRecoveryPoint = ptr->minRecoveryPoint;
-#else
-		fprintf(stderr, "ERROR: please use a repmgr version built for PostgreSQL 12 or later\n");
-		exit(ERR_BAD_CONFIG);
-#endif
-	}
-	else if (version_num >= 110000)
-	{
-		ControlFileData11 *ptr = (struct ControlFileData11 *)ControlFileDataPtr;
-		control_file_info->system_identifier = ptr->system_identifier;
-		control_file_info->state = ptr->state;
-		control_file_info->checkPoint = ptr->checkPoint;
-		control_file_info->data_checksum_version = ptr->data_checksum_version;
-		control_file_info->timeline = ptr->checkPointCopy.ThisTimeLineID;
-		control_file_info->minRecoveryPointTLI = ptr->minRecoveryPointTLI;
-		control_file_info->minRecoveryPoint = ptr->minRecoveryPoint;
-	}
-	else if (version_num >= 90500)
-	{
-		ControlFileData95 *ptr = (struct ControlFileData95 *)ControlFileDataPtr;
-		control_file_info->system_identifier = ptr->system_identifier;
-		control_file_info->state = ptr->state;
-		control_file_info->checkPoint = ptr->checkPoint;
-		control_file_info->data_checksum_version = ptr->data_checksum_version;
-		control_file_info->timeline = ptr->checkPointCopy.ThisTimeLineID;
-		control_file_info->minRecoveryPointTLI = ptr->minRecoveryPointTLI;
-		control_file_info->minRecoveryPoint = ptr->minRecoveryPoint;
-	}
-	else if (version_num >= 90400)
-	{
-		ControlFileData94 *ptr = (struct ControlFileData94 *)ControlFileDataPtr;
-		control_file_info->system_identifier = ptr->system_identifier;
-		control_file_info->state = ptr->state;
-		control_file_info->checkPoint = ptr->checkPoint;
-		control_file_info->data_checksum_version = ptr->data_checksum_version;
-		control_file_info->timeline = ptr->checkPointCopy.ThisTimeLineID;
-		control_file_info->minRecoveryPointTLI = ptr->minRecoveryPointTLI;
-		control_file_info->minRecoveryPoint = ptr->minRecoveryPoint;
-	}
-
-	pfree(ControlFileDataPtr);
-
 	/*
 	 * We don't check the CRC here as we're potentially checking a pg_control
 	 * file from a different PostgreSQL version to the one repmgr was compiled
-	 * against.
+	 * against. However we're only interested in the first few fields, which
+	 * should be constant across supported versions
+	 *
 	 */
 
 	return control_file_info;

controldata.h

@@ -1,6 +1,6 @@
 /*
  * controldata.h
- * Copyright (c) EnterpriseDB Corporation, 2010-2021
+ * Copyright (c) 2ndQuadrant, 2010-2017
  *
  * Portions Copyright (c) 1996-2016, PostgreSQL Global Development Group
  * Portions Copyright (c) 1994, Regents of the University of California
@@ -12,378 +12,16 @@
 #include "postgres_fe.h"
 #include "catalog/pg_control.h"
 
-
-#define MAX_VERSION_STRING 24
-/*
- * A simplified representation of pg_control containing only those fields
- * required by repmgr.
- */
 typedef struct
 {
 	bool		control_file_processed;
-	uint64		system_identifier;
+	ControlFileData *control_file;
-	DBState		state;
-	XLogRecPtr	checkPoint;
-	uint32		data_checksum_version;
-	TimeLineID	timeline;
-	TimeLineID	minRecoveryPointTLI;
-	XLogRecPtr	minRecoveryPoint;
 } ControlFileInfo;
 
-
+extern DBState get_db_state(const char *data_directory);
-typedef struct CheckPoint94
-{
-	XLogRecPtr	redo;			/* next RecPtr available when we began to
-								 * create CheckPoint (i.e. REDO start point) */
-	TimeLineID	ThisTimeLineID; /* current TLI */
-	TimeLineID	PrevTimeLineID; /* previous TLI, if this record begins a new
-								 * timeline (equals ThisTimeLineID otherwise) */
-	bool		fullPageWrites; /* current full_page_writes */
-	uint32		nextXidEpoch;	/* higher-order bits of nextXid */
-	TransactionId nextXid;		/* next free XID */
-	Oid			nextOid;		/* next free OID */
-	MultiXactId nextMulti;		/* next free MultiXactId */
-	MultiXactOffset nextMultiOffset;	/* next free MultiXact offset */
-	TransactionId oldestXid;	/* cluster-wide minimum datfrozenxid */
-	Oid			oldestXidDB;	/* database with minimum datfrozenxid */
-	MultiXactId oldestMulti;	/* cluster-wide minimum datminmxid */
-	Oid			oldestMultiDB;	/* database with minimum datminmxid */
-	pg_time_t	time;			/* time stamp of checkpoint */
-
-	TransactionId oldestActiveXid;
-} CheckPoint94;
-
-
-/* Same for 9.5, 9.6, 10, 11 */
-typedef struct CheckPoint95
-{
-	XLogRecPtr	redo;			/* next RecPtr available when we began to
-								 * create CheckPoint (i.e. REDO start point) */
-	TimeLineID	ThisTimeLineID; /* current TLI */
-	TimeLineID	PrevTimeLineID; /* previous TLI, if this record begins a new
-								 * timeline (equals ThisTimeLineID otherwise) */
-	bool		fullPageWrites; /* current full_page_writes */
-	uint32		nextXidEpoch;	/* higher-order bits of nextXid */
-	TransactionId nextXid;		/* next free XID */
-	Oid			nextOid;		/* next free OID */
-	MultiXactId nextMulti;		/* next free MultiXactId */
-	MultiXactOffset nextMultiOffset;	/* next free MultiXact offset */
-	TransactionId oldestXid;	/* cluster-wide minimum datfrozenxid */
-	Oid			oldestXidDB;	/* database with minimum datfrozenxid */
-	MultiXactId oldestMulti;	/* cluster-wide minimum datminmxid */
-	Oid			oldestMultiDB;	/* database with minimum datminmxid */
-	pg_time_t	time;			/* time stamp of checkpoint */
-	TransactionId oldestCommitTsXid;	/* oldest Xid with valid commit
-										 * timestamp */
-	TransactionId newestCommitTsXid;	/* newest Xid with valid commit
-										 * timestamp */
-
-	TransactionId oldestActiveXid;
-} CheckPoint95;
-
-
-#if PG_ACTUAL_VERSION_NUM >= 120000
-/*
- * Following fields removed in PostgreSQL 12;
- *
- *   uint32 nextXidEpoch;
- *   TransactionId nextXid;
- *
- * and replaced by:
- *
- *   FullTransactionId nextFullXid;
- */
-
-typedef struct CheckPoint12
-{
-	XLogRecPtr	redo;			/* next RecPtr available when we began to
-								 * create CheckPoint (i.e. REDO start point) */
-	TimeLineID	ThisTimeLineID; /* current TLI */
-	TimeLineID	PrevTimeLineID; /* previous TLI, if this record begins a new
-								 * timeline (equals ThisTimeLineID otherwise) */
-	bool		fullPageWrites; /* current full_page_writes */
-	FullTransactionId nextFullXid;	/* next free full transaction ID */
-	Oid			nextOid;		/* next free OID */
-	MultiXactId nextMulti;		/* next free MultiXactId */
-	MultiXactOffset nextMultiOffset;	/* next free MultiXact offset */
-	TransactionId oldestXid;	/* cluster-wide minimum datfrozenxid */
-	Oid			oldestXidDB;	/* database with minimum datfrozenxid */
-	MultiXactId oldestMulti;	/* cluster-wide minimum datminmxid */
-	Oid			oldestMultiDB;	/* database with minimum datminmxid */
-	pg_time_t	time;			/* time stamp of checkpoint */
-	TransactionId oldestCommitTsXid;	/* oldest Xid with valid commit
-										 * timestamp */
-	TransactionId newestCommitTsXid;	/* newest Xid with valid commit
-										 * timestamp */
-
-	/*
-	 * Oldest XID still running. This is only needed to initialize hot standby
-	 * mode from an online checkpoint, so we only bother calculating this for
-	 * online checkpoints and only when wal_level is replica. Otherwise it's
-	 * set to InvalidTransactionId.
-	 */
-	TransactionId oldestActiveXid;
-} CheckPoint12;
-#endif
-
-
-typedef struct ControlFileData94
-{
-	uint64		system_identifier;
-
-	uint32		pg_control_version;		/* PG_CONTROL_VERSION */
-	uint32		catalog_version_no;		/* see catversion.h */
-
-	DBState		state;			/* see enum above */
-	pg_time_t	time;			/* time stamp of last pg_control update */
-	XLogRecPtr	checkPoint;		/* last check point record ptr */
-	XLogRecPtr	prevCheckPoint; /* previous check point record ptr */
-
-	CheckPoint94	checkPointCopy; /* copy of last check point record */
-
-	XLogRecPtr	unloggedLSN;	/* current fake LSN value, for unlogged rels */
-
-	XLogRecPtr	minRecoveryPoint;
-	TimeLineID	minRecoveryPointTLI;
-	XLogRecPtr	backupStartPoint;
-	XLogRecPtr	backupEndPoint;
-	bool		backupEndRequired;
-
-	int			wal_level;
-	bool		wal_log_hints;
-	int			MaxConnections;
-	int			max_worker_processes;
-	int			max_prepared_xacts;
-	int			max_locks_per_xact;
-
-	uint32		maxAlign;		/* alignment requirement for tuples */
-	double		floatFormat;	/* constant 1234567.0 */
-
-	uint32		blcksz;			/* data block size for this DB */
-	uint32		relseg_size;	/* blocks per segment of large relation */
-
-	uint32		xlog_blcksz;	/* block size within WAL files */
-	uint32		xlog_seg_size;	/* size of each WAL segment */
-
-	uint32		nameDataLen;	/* catalog name field width */
-	uint32		indexMaxKeys;	/* max number of columns in an index */
-
-	uint32		toast_max_chunk_size;	/* chunk size in TOAST tables */
-	uint32		loblksize;		/* chunk size in pg_largeobject */
-
-	bool		enableIntTimes; /* int64 storage enabled? */
-
-	bool		float4ByVal;	/* float4 pass-by-value? */
-	bool		float8ByVal;	/* float8, int8, etc pass-by-value? */
-
-	/* Are data pages protected by checksums? Zero if no checksum version */
-	uint32		data_checksum_version;
-
-} ControlFileData94;
-
-
-
-/*
- * Following field added since 9.4:
- *
- *	bool		track_commit_timestamp;
- *
- * Unchanged in 9.6
- *
- * In 10, following field appended *after* "data_checksum_version":
- *
- *	char		mock_authentication_nonce[MOCK_AUTH_NONCE_LEN];
- *
- * (but we don't care about that)
- */
-
-typedef struct ControlFileData95
-{
-	uint64		system_identifier;
-
-	uint32		pg_control_version;		/* PG_CONTROL_VERSION */
-	uint32		catalog_version_no;		/* see catversion.h */
-
-	DBState		state;			/* see enum above */
-	pg_time_t	time;			/* time stamp of last pg_control update */
-	XLogRecPtr	checkPoint;		/* last check point record ptr */
-	XLogRecPtr	prevCheckPoint; /* previous check point record ptr */
-
-	CheckPoint95	checkPointCopy; /* copy of last check point record */
-
-	XLogRecPtr	unloggedLSN;	/* current fake LSN value, for unlogged rels */
-
-	XLogRecPtr	minRecoveryPoint;
-	TimeLineID	minRecoveryPointTLI;
-	XLogRecPtr	backupStartPoint;
-	XLogRecPtr	backupEndPoint;
-	bool		backupEndRequired;
-
-	int			wal_level;
-	bool		wal_log_hints;
-	int			MaxConnections;
-	int			max_worker_processes;
-	int			max_prepared_xacts;
-	int			max_locks_per_xact;
-	bool		track_commit_timestamp;
-
-	uint32		maxAlign;		/* alignment requirement for tuples */
-	double		floatFormat;	/* constant 1234567.0 */
-
-	uint32		blcksz;			/* data block size for this DB */
-	uint32		relseg_size;	/* blocks per segment of large relation */
-
-	uint32		xlog_blcksz;	/* block size within WAL files */
-	uint32		xlog_seg_size;	/* size of each WAL segment */
-
-	uint32		nameDataLen;	/* catalog name field width */
-	uint32		indexMaxKeys;	/* max number of columns in an index */
-
-	uint32		toast_max_chunk_size;	/* chunk size in TOAST tables */
-	uint32		loblksize;		/* chunk size in pg_largeobject */
-
-	bool		enableIntTimes; /* int64 storage enabled? */
-
-	bool		float4ByVal;	/* float4 pass-by-value? */
-	bool		float8ByVal;	/* float8, int8, etc pass-by-value? */
-
-	uint32		data_checksum_version;
-
-} ControlFileData95;
-
-/*
- * Following field removed in 11:
- *
- *  XLogRecPtr	prevCheckPoint;
- *
- * In 10, following field appended *after* "data_checksum_version":
- *
- * 	char		mock_authentication_nonce[MOCK_AUTH_NONCE_LEN];
- *
- * (but we don't care about that)
- */
-
-typedef struct ControlFileData11
-{
-	uint64		system_identifier;
-
-	uint32		pg_control_version;		/* PG_CONTROL_VERSION */
-	uint32		catalog_version_no;		/* see catversion.h */
-
-	DBState		state;			/* see enum above */
-	pg_time_t	time;			/* time stamp of last pg_control update */
-	XLogRecPtr	checkPoint;		/* last check point record ptr */
-
-	CheckPoint95	checkPointCopy; /* copy of last check point record */
-
-	XLogRecPtr	unloggedLSN;	/* current fake LSN value, for unlogged rels */
-
-	XLogRecPtr	minRecoveryPoint;
-	TimeLineID	minRecoveryPointTLI;
-	XLogRecPtr	backupStartPoint;
-	XLogRecPtr	backupEndPoint;
-	bool		backupEndRequired;
-
-	int			wal_level;
-	bool		wal_log_hints;
-	int			MaxConnections;
-	int			max_worker_processes;
-	int			max_prepared_xacts;
-	int			max_locks_per_xact;
-	bool		track_commit_timestamp;
-
-	uint32		maxAlign;		/* alignment requirement for tuples */
-	double		floatFormat;	/* constant 1234567.0 */
-
-	uint32		blcksz;			/* data block size for this DB */
-	uint32		relseg_size;	/* blocks per segment of large relation */
-
-	uint32		xlog_blcksz;	/* block size within WAL files */
-	uint32		xlog_seg_size;	/* size of each WAL segment */
-
-	uint32		nameDataLen;	/* catalog name field width */
-	uint32		indexMaxKeys;	/* max number of columns in an index */
-
-	uint32		toast_max_chunk_size;	/* chunk size in TOAST tables */
-	uint32		loblksize;		/* chunk size in pg_largeobject */
-
-	bool		enableIntTimes; /* int64 storage enabled? */
-
-	bool		float4ByVal;	/* float4 pass-by-value? */
-	bool		float8ByVal;	/* float8, int8, etc pass-by-value? */
-
-	uint32		data_checksum_version;
-
-} ControlFileData11;
-
-
-#if PG_ACTUAL_VERSION_NUM >= 120000
-/*
- * Following field added in Pg12:
- *
- *   int max_wal_senders;
- */
-
-typedef struct ControlFileData12
-{
-	uint64		system_identifier;
-
-	uint32		pg_control_version; /* PG_CONTROL_VERSION */
-	uint32		catalog_version_no; /* see catversion.h */
-
-	DBState		state;			/* see enum above */
-	pg_time_t	time;			/* time stamp of last pg_control update */
-	XLogRecPtr	checkPoint;		/* last check point record ptr */
-
-	CheckPoint12	checkPointCopy; /* copy of last check point record */
-
-	XLogRecPtr	unloggedLSN;	/* current fake LSN value, for unlogged rels */
-
-	XLogRecPtr	minRecoveryPoint;
-	TimeLineID	minRecoveryPointTLI;
-	XLogRecPtr	backupStartPoint;
-	XLogRecPtr	backupEndPoint;
-	bool		backupEndRequired;
-
-	int			wal_level;
-	bool		wal_log_hints;
-	int			MaxConnections;
-	int			max_worker_processes;
-	int			max_wal_senders;
-	int			max_prepared_xacts;
-	int			max_locks_per_xact;
-	bool		track_commit_timestamp;
-
-	uint32		maxAlign;		/* alignment requirement for tuples */
-	double		floatFormat;	/* constant 1234567.0 */
-
-	uint32		blcksz;			/* data block size for this DB */
-	uint32		relseg_size;	/* blocks per segment of large relation */
-
-	uint32		xlog_blcksz;	/* block size within WAL files */
-	uint32		xlog_seg_size;	/* size of each WAL segment */
-
-	uint32		nameDataLen;	/* catalog name field width */
-	uint32		indexMaxKeys;	/* max number of columns in an index */
-
-	uint32		toast_max_chunk_size;	/* chunk size in TOAST tables */
-	uint32		loblksize;		/* chunk size in pg_largeobject */
-
-	bool		float4ByVal;	/* float4 pass-by-value? */
-	bool		float8ByVal;	/* float8, int8, etc pass-by-value? */
-
-	uint32		data_checksum_version;
-} ControlFileData12;
-#endif
-
-extern int get_pg_version(const char *data_directory, char *version_string);
-extern bool get_db_state(const char *data_directory, DBState *state);
 extern const char *describe_db_state(DBState state);
 extern int	get_data_checksum_version(const char *data_directory);
 extern uint64 get_system_identifier(const char *data_directory);
 extern XLogRecPtr get_latest_checkpoint_location(const char *data_directory);
-extern TimeLineID get_timeline(const char *data_directory);
-extern TimeLineID get_min_recovery_end_timeline(const char *data_directory);
-extern XLogRecPtr get_min_recovery_location(const char *data_directory);
 
 #endif							/* _CONTROLDATA_H_ */

dbutils.h

@@ -1,7 +1,7 @@
 /*
  * dbutils.h
  *
- * Copyright (c) EnterpriseDB Corporation, 2010-2021
+ * Copyright (c) 2ndQuadrant, 2010-2017
  *
  * This program is free software: you can redistribute it and/or modify
  * it under the terms of the GNU General Public License as published by
@@ -20,7 +20,6 @@
 #ifndef _REPMGR_DBUTILS_H_
 #define _REPMGR_DBUTILS_H_
 
-#include "access/timeline.h"
 #include "access/xlogdefs.h"
 #include "pqexpbuffer.h"
 #include "portability/instr_time.h"
@@ -29,36 +28,8 @@
 #include "strutil.h"
 #include "voting.h"
 
-#define REPMGR_NODES_COLUMNS \
+#define REPMGR_NODES_COLUMNS "node_id, type, upstream_node_id, node_name, conninfo, repluser, slot_name, location, priority, active, config_file, '' AS upstream_node_name "
-	"n.node_id, " \
+#define BDR_NODES_COLUMNS "node_sysid, node_timeline, node_dboid, node_status, node_name, node_local_dsn, node_init_from_dsn, node_read_only, node_seq_id"
-	"n.type, " \
-	"n.upstream_node_id, " \
-	"n.node_name,  " \
-	"n.conninfo, " \
-	"n.repluser, " \
-	"n.slot_name, " \
-	"n.location, " \
-	"n.priority, " \
-	"n.active, " \
-	"n.config_file, " \
-	"'' AS upstream_node_name, " \
-	"NULL AS attached "
-
-#define REPMGR_NODES_COLUMNS_WITH_UPSTREAM \
-	"n.node_id, " \
-	"n.type, " \
-	"n.upstream_node_id, " \
-	"n.node_name, " \
-	"n.conninfo, " \
-	"n.repluser, " \
-	"n.slot_name, " \
-	"n.location, " \
-	"n.priority, " \
-	"n.active, "\
-	"n.config_file, " \
-	"un.node_name AS upstream_node_name, " \
-	"NULL AS attached "
-
 
 #define ERRBUFF_SIZE 512
 
@@ -67,13 +38,12 @@ typedef enum
 	UNKNOWN = 0,
 	PRIMARY,
 	STANDBY,
-	WITNESS
+	BDR
 } t_server_type;
 
 typedef enum
 {
 	REPMGR_INSTALLED = 0,
-	REPMGR_OLD_VERSION_INSTALLED,
 	REPMGR_AVAILABLE,
 	REPMGR_UNAVAILABLE,
 	REPMGR_UNKNOWN
@@ -103,91 +73,27 @@ typedef enum
 {
 	NODE_STATUS_UNKNOWN = -1,
 	NODE_STATUS_UP,
-	NODE_STATUS_SHUTTING_DOWN,
 	NODE_STATUS_DOWN,
-	NODE_STATUS_UNCLEAN_SHUTDOWN,
+	NODE_STATUS_UNCLEAN_SHUTDOWN
-	NODE_STATUS_REJECTED
 } NodeStatus;
 
 typedef enum
 {
-	CONN_UNKNOWN = -1,
+	VR_VOTE_REFUSED = -1,
-	CONN_OK,
+	VR_POSITIVE_VOTE,
-	CONN_BAD,
+	VR_NEGATIVE_VOTE
-	CONN_ERROR
+} VoteRequestResult;
-} ConnectionStatus;
 
-typedef enum
-{
-	/* unable to query "pg_stat_replication" or other error */
-	NODE_ATTACHED_UNKNOWN = -1,
-	/* node has record in "pg_stat_replication" and state is not "streaming" */
-	NODE_ATTACHED,
-	/* node has record in "pg_stat_replication" but state is not "streaming" */
-	NODE_NOT_ATTACHED,
-	/* node has no record in "pg_stat_replication" */
-	NODE_DETACHED
-} NodeAttached;
 
 typedef enum
 {
 	SLOT_UNKNOWN = -1,
-	SLOT_NOT_FOUND,
-	SLOT_NOT_PHYSICAL,
 	SLOT_INACTIVE,
 	SLOT_ACTIVE
 } ReplSlotStatus;
 
-typedef enum
-{
-	BACKUP_STATE_UNKNOWN = -1,
-	BACKUP_STATE_IN_BACKUP,
-	BACKUP_STATE_NO_BACKUP
-} BackupState;
-
-
-
 /*
- * Struct to store extension version information
+ * Struct to store node information
- */
-
-typedef struct s_extension_versions {
-	char		default_version[8];
-	int			default_version_num;
-	char		installed_version[8];
-	int			installed_version_num;
-} t_extension_versions;
-
-#define T_EXTENSION_VERSIONS_INITIALIZER { \
-	"", \
-	UNKNOWN_SERVER_VERSION_NUM, \
-	"", \
-	UNKNOWN_SERVER_VERSION_NUM \
-}
-
-
-typedef struct
-{
-	char		current_timestamp[MAXLEN];
-	bool		in_recovery;
-	TimeLineID	timeline_id;
-	char		timeline_id_str[MAXLEN];
-	XLogRecPtr	last_wal_receive_lsn;
-	XLogRecPtr	last_wal_replay_lsn;
-	char		last_xact_replay_timestamp[MAXLEN];
-	int			replication_lag_time;
-	bool		receiving_streamed_wal;
-	bool		wal_replay_paused;
-	int			upstream_last_seen;
-	int			upstream_node_id;
-} ReplInfo;
-
-/*
- * Struct to store node information.
- *
- * The first section represents the contents of the "repmgr.nodes"
- * table; subsequent section contain information collated in
- * various contexts.
  */
 typedef struct s_node_info
 {
@@ -195,8 +101,8 @@ typedef struct s_node_info
 	int			node_id;
 	int			upstream_node_id;
 	t_server_type type;
-	char		node_name[NAMEDATALEN];
+	char		node_name[MAXLEN];
-	char		upstream_node_name[NAMEDATALEN];
+	char		upstream_node_name[MAXLEN];
 	char		conninfo[MAXLEN];
 	char		repluser[NAMEDATALEN];
 	char		location[MAXLEN];
@@ -213,7 +119,7 @@ typedef struct s_node_info
 	/* for ad-hoc use e.g. when working with a list of nodes */
 	char		details[MAXLEN];
 	bool		reachable;
-	NodeAttached attached;
+	bool		attached;
 	/* various statistics */
 	int			max_wal_senders;
 	int			attached_wal_receivers;
@@ -221,8 +127,6 @@ typedef struct s_node_info
 	int			total_replication_slots;
 	int			active_replication_slots;
 	int			inactive_replication_slots;
-	/* replication info */
-	ReplInfo   *replication_info;
 } t_node_info;
 
 
@@ -247,10 +151,9 @@ typedef struct s_node_info
 	MS_NORMAL, \
 	NULL, \
 	/* for ad-hoc use e.g. when working with a list of nodes */ \
-	"", true, true,	\
+	"", true, true \
 	/* various statistics */ \
-	-1, -1, -1, -1, -1, -1,	\
+	-1, -1, -1, -1, -1, -1					\
-	NULL \
 }
 
 
@@ -278,13 +181,11 @@ typedef struct s_event_info
 {
 	char	   *node_name;
 	char	   *conninfo_str;
-	int			node_id;
 } t_event_info;
 
 #define T_EVENT_INFO_INITIALIZER { \
 	NULL, \
-	NULL, \
+ 	NULL \
-	UNKNOWN_NODE_ID \
 }
 
 
@@ -326,6 +227,66 @@ typedef struct s_connection_user
 #define T_CONNECTION_USER_INITIALIZER { "", false }
 
 
+/* represents an entry in bdr.bdr_nodes */
+typedef struct s_bdr_node_info
+{
+	char		node_sysid[MAXLEN];
+	uint32		node_timeline;
+	uint32		node_dboid;
+	char		node_status;
+	char		node_name[MAXLEN];
+	char		node_local_dsn[MAXLEN];
+	char		node_init_from_dsn[MAXLEN];
+	bool		read_only;
+	uint32		node_seq_id;
+} t_bdr_node_info;
+
+#define T_BDR_NODE_INFO_INITIALIZER { \
+	"", InvalidOid, InvalidOid, \
+	'?', "", "", "", \
+    false, -1 \
+}
+
+
+/* structs to store a list of BDR node records */
+typedef struct BdrNodeInfoListCell
+{
+	struct BdrNodeInfoListCell *next;
+	t_bdr_node_info *node_info;
+} BdrNodeInfoListCell;
+
+typedef struct BdrNodeInfoList
+{
+	BdrNodeInfoListCell *head;
+	BdrNodeInfoListCell *tail;
+	int			node_count;
+} BdrNodeInfoList;
+
+#define T_BDR_NODE_INFO_LIST_INITIALIZER { \
+	NULL, \
+	NULL, \
+	0 \
+}
+
+typedef struct
+{
+	char		current_timestamp[MAXLEN];
+	uint64		last_wal_receive_lsn;
+	uint64		last_wal_replay_lsn;
+	char		last_xact_replay_timestamp[MAXLEN];
+	int			replication_lag_time;
+	bool		receiving_streamed_wal;
+} ReplInfo;
+
+#define T_REPLINFO_INTIALIZER { \
+	"", \
+	InvalidXLogRecPtr, \
+	InvalidXLogRecPtr, \
+	"", \
+	0 \
+}
+
+
 typedef struct
 {
 	char		filepath[MAXPGPATH];
@@ -335,7 +296,6 @@ typedef struct
 
 #define T_CONFIGFILE_INFO_INITIALIZER { "", "", false }
 
-
 typedef struct
 {
 	int			size;
@@ -345,7 +305,6 @@ typedef struct
 
 #define T_CONFIGFILE_LIST_INITIALIZER { 0, 0, NULL }
 
-
 typedef struct
 {
 	uint64		system_identifier;
@@ -358,24 +317,9 @@ typedef struct
     UNKNOWN_TIMELINE_ID, \
 	InvalidXLogRecPtr \
 }
+/* global variables */
 
-
+extern int	server_version_num;
-typedef struct RepmgrdInfo {
-	int node_id;
-	int pid;
-	char pid_text[MAXLEN];
-	char pid_file[MAXLEN];
-	bool pg_running;
-	char pg_running_text[MAXLEN];
-	RecoveryType recovery_type;
-	bool running;
-	char repmgrd_running[MAXLEN];
-	bool paused;
-	bool wal_paused_pending_wal;
-	int  upstream_last_seen;
-	char upstream_last_seen_text[MAXLEN];
-} RepmgrdInfo;
-
 
 /* macros */
 
@@ -385,32 +329,33 @@ typedef struct RepmgrdInfo {
 /* utility functions */
 
 XLogRecPtr	parse_lsn(const char *str);
+
+extern void
+wrap_ddl_query(PQExpBufferData *query_buf, int replication_type, const char *fmt,...)
+__attribute__((format(PG_PRINTF_ATTRIBUTE, 3, 4)));
 bool		atobool(const char *value);
 
 /* connection functions */
-PGconn	   *establish_db_connection(const char *conninfo,
+PGconn *establish_db_connection(const char *conninfo,
 						const bool exit_on_error);
 PGconn	   *establish_db_connection_quiet(const char *conninfo);
-PGconn	   *establish_db_connection_by_params(t_conninfo_param_list *param_list,
+PGconn *establish_db_connection_as_user(const char *conninfo,
-								  const bool exit_on_error);
+								const char *user,
-PGconn	   *establish_db_connection_with_replacement_param(const char *conninfo,
-														   const char *param,
-														   const char *value,
-														   const bool exit_on_error);
-PGconn	   *establish_replication_connection_from_conn(PGconn *conn, const char *repluser);
-PGconn	   *establish_replication_connection_from_conninfo(const char *conninfo, const char *repluser);
-
-PGconn	   *establish_primary_db_connection(PGconn *conn,
 								const bool exit_on_error);
+
+PGconn *establish_db_connection_by_params(t_conninfo_param_list *param_list,
+								  const bool exit_on_error);
+PGconn *establish_primary_db_connection(PGconn *conn,
+								const bool exit_on_error);
+
 PGconn	   *get_primary_connection(PGconn *standby_conn, int *primary_id, char *primary_conninfo_out);
 PGconn	   *get_primary_connection_quiet(PGconn *standby_conn, int *primary_id, char *primary_conninfo_out);
-PGconn	   *duplicate_connection(PGconn *conn, const char *user, bool replication);
 
-void		close_connection(PGconn **conn);
+bool		is_superuser_connection(PGconn *conn, t_connection_user *userinfo);
 
 /* conninfo manipulation functions */
 bool		get_conninfo_value(const char *conninfo, const char *keyword, char *output);
-bool		get_conninfo_default_value(const char *param, char *output, int maxlen);
+
 void		initialize_conninfo_params(t_conninfo_param_list *param_list, bool set_defaults);
 void		free_conninfo_params(t_conninfo_param_list *param_list);
 void		copy_conninfo_params(t_conninfo_param_list *dest_list, t_conninfo_param_list *source_list);
@@ -418,108 +363,68 @@ void		conn_to_param_list(PGconn *conn, t_conninfo_param_list *param_list);
 void		param_set(t_conninfo_param_list *param_list, const char *param, const char *value);
 void		param_set_ine(t_conninfo_param_list *param_list, const char *param, const char *value);
 char	   *param_get(t_conninfo_param_list *param_list, const char *param);
-bool		validate_conninfo_string(const char *conninfo_str, char **errmsg);
+bool		parse_conninfo_string(const char *conninfo_str, t_conninfo_param_list *param_list, char *errmsg, bool ignore_local_params);
-bool		parse_conninfo_string(const char *conninfo_str, t_conninfo_param_list *param_list, char **errmsg, bool ignore_local_params);
 char	   *param_list_to_string(t_conninfo_param_list *param_list);
-char	   *normalize_conninfo_string(const char *conninfo_str);
-bool		has_passfile(void);
-
 
 /* transaction functions */
 bool		begin_transaction(PGconn *conn);
 bool		commit_transaction(PGconn *conn);
 bool		rollback_transaction(PGconn *conn);
+bool		check_cluster_schema(PGconn *conn);
 
 /* GUC manipulation functions */
 bool		set_config(PGconn *conn, const char *config_param, const char *config_value);
 bool		set_config_bool(PGconn *conn, const char *config_param, bool state);
-int		    guc_set(PGconn *conn, const char *parameter, const char *op, const char *value);
+int guc_set(PGconn *conn, const char *parameter, const char *op,
+		const char *value);
+int guc_set_typed(PGconn *conn, const char *parameter, const char *op,
+			  const char *value, const char *datatype);
 bool		get_pg_setting(PGconn *conn, const char *setting, char *output);
-bool		get_pg_setting_bool(PGconn *conn, const char *setting, bool *output);
-bool		get_pg_setting_int(PGconn *conn, const char *setting, int *output);
-bool		alter_system_int(PGconn *conn, const char *name, int value);
-bool		pg_reload_conf(PGconn *conn);
 
 /* server information functions */
 bool		get_cluster_size(PGconn *conn, char *size);
-int			get_server_version(PGconn *conn, char *server_version_buf);
+int			get_server_version(PGconn *conn, char *server_version);
-
 RecoveryType get_recovery_type(PGconn *conn);
 int			get_primary_node_id(PGconn *conn);
+bool		can_use_pg_rewind(PGconn *conn, const char *data_directory, PQExpBufferData *reason);
 int			get_ready_archive_files(PGconn *conn, const char *data_directory);
 bool		identify_system(PGconn *repl_conn, t_system_identification *identification);
-uint64		system_identifier(PGconn *conn);
-TimeLineHistoryEntry *get_timeline_history(PGconn *repl_conn, TimeLineID tli);
-pid_t		get_wal_receiver_pid(PGconn *conn);
-
-/* user/role information functions */
-bool		can_execute_checkpoint(PGconn *conn);
-bool		can_execute_pg_promote(PGconn *conn);
-bool		can_disable_walsender(PGconn *conn);
-bool		connection_has_pg_monitor_role(PGconn *conn, const char *subrole);
-bool		is_replication_role(PGconn *conn, char *rolname);
-bool		is_superuser_connection(PGconn *conn, t_connection_user *userinfo);
-
-/* repmgrd shared memory functions */
 bool		repmgrd_set_local_node_id(PGconn *conn, int local_node_id);
-int			repmgrd_get_local_node_id(PGconn *conn);
-bool		repmgrd_check_local_node_id(PGconn *conn);
-BackupState	server_in_exclusive_backup_mode(PGconn *conn);
-void		repmgrd_set_pid(PGconn *conn, pid_t repmgrd_pid, const char *pidfile);
-pid_t		repmgrd_get_pid(PGconn *conn);
-bool		repmgrd_is_running(PGconn *conn);
-bool		repmgrd_is_paused(PGconn *conn);
-bool		repmgrd_pause(PGconn *conn, bool pause);
-int			repmgrd_get_upstream_node_id(PGconn *conn);
-bool		repmgrd_set_upstream_node_id(PGconn *conn, int node_id);
 
 /* extension functions */
-ExtensionStatus get_repmgr_extension_status(PGconn *conn, t_extension_versions *extversions);
+ExtensionStatus get_repmgr_extension_status(PGconn *conn);
 
 /* node management functions */
 void		checkpoint(PGconn *conn);
 bool		vacuum_table(PGconn *conn, const char *table);
-bool		promote_standby(PGconn *conn, bool wait, int wait_seconds);
+
-bool		resume_wal_replay(PGconn *conn);
 
 /* node record functions */
 t_server_type parse_node_type(const char *type);
 const char *get_node_type_string(t_server_type type);
 
 RecordStatus get_node_record(PGconn *conn, int node_id, t_node_info *node_info);
-RecordStatus refresh_node_record(PGconn *conn, int node_id, t_node_info *node_info);
-
-RecordStatus get_node_record_with_upstream(PGconn *conn, int node_id, t_node_info *node_info);
-
 RecordStatus get_node_record_by_name(PGconn *conn, const char *node_name, t_node_info *node_info);
 t_node_info *get_node_record_pointer(PGconn *conn, int node_id);
 
 bool		get_local_node_record(PGconn *conn, int node_id, t_node_info *node_info);
 bool		get_primary_node_record(PGconn *conn, t_node_info *node_info);
 
-bool		get_all_node_records(PGconn *conn, NodeInfoList *node_list);
+void		get_all_node_records(PGconn *conn, NodeInfoList *node_list);
-bool		get_all_nodes_count(PGconn *conn, int *count);
 void		get_downstream_node_records(PGconn *conn, int node_id, NodeInfoList *nodes);
 void		get_active_sibling_node_records(PGconn *conn, int node_id, int upstream_node_id, NodeInfoList *node_list);
-bool		get_child_nodes(PGconn *conn, int node_id, NodeInfoList *node_list);
 void		get_node_records_by_priority(PGconn *conn, NodeInfoList *node_list);
-bool		get_all_node_records_with_upstream(PGconn *conn, NodeInfoList *node_list);
+void		get_all_node_records_with_upstream(PGconn *conn, NodeInfoList *node_list);
-bool		get_downstream_nodes_with_missing_slot(PGconn *conn, int this_node_id, NodeInfoList *noede_list);
 
 bool		create_node_record(PGconn *conn, char *repmgr_action, t_node_info *node_info);
 bool		update_node_record(PGconn *conn, char *repmgr_action, t_node_info *node_info);
 bool		delete_node_record(PGconn *conn, int node);
-bool		truncate_node_records(PGconn *conn);
 
 bool		update_node_record_set_active(PGconn *conn, int this_node_id, bool active);
 bool		update_node_record_set_primary(PGconn *conn, int this_node_id);
-bool		update_node_record_set_active_standby(PGconn *conn, int this_node_id);
 bool		update_node_record_set_upstream(PGconn *conn, int this_node_id, int new_upstream_node_id);
 bool		update_node_record_status(PGconn *conn, int this_node_id, char *type, int upstream_node_id, bool active);
 bool		update_node_record_conn_priority(PGconn *conn, t_configuration_options *options);
-bool		update_node_record_slot_name(PGconn *primary_conn, int node_id, char *slot_name);
-
-bool		witness_copy_node_records(PGconn *primary_conn, PGconn *witness_conn);
 
 void		clear_node_info_list(NodeInfoList *nodes);
 
@@ -533,33 +438,21 @@ void		config_file_list_add(t_configfile_list *list, const char *file, const char
 bool		create_event_record(PGconn *conn, t_configuration_options *options, int node_id, char *event, bool successful, char *details);
 bool		create_event_notification(PGconn *conn, t_configuration_options *options, int node_id, char *event, bool successful, char *details);
 bool		create_event_notification_extended(PGconn *conn, t_configuration_options *options, int node_id, char *event, bool successful, char *details, t_event_info *event_info);
-PGresult   *get_event_records(PGconn *conn, int node_id, const char *node_name, const char *event, bool all, int limit);
 
 /* replication slot functions */
-void		create_slot_name(char *slot_name, int node_id);
+bool		create_replication_slot(PGconn *conn, char *slot_name, int server_version_num, PQExpBufferData *error_msg);
-
+bool		drop_replication_slot(PGconn *conn, char *slot_name);
-bool		create_replication_slot_sql(PGconn *conn, char *slot_name, PQExpBufferData *error_msg);
-bool		create_replication_slot_replprot(PGconn *conn, PGconn *repl_conn, char *slot_name, PQExpBufferData *error_msg);
-bool		drop_replication_slot_sql(PGconn *conn, char *slot_name);
-bool		drop_replication_slot_replprot(PGconn *repl_conn, char *slot_name);
-
 RecordStatus get_slot_record(PGconn *conn, char *slot_name, t_replication_slot *record);
-int			get_free_replication_slot_count(PGconn *conn, int *max_replication_slots);
-int			get_inactive_replication_slots(PGconn *conn, KeyValueList *list);
 
 /* tablespace functions */
 bool		get_tablespace_name_by_location(PGconn *conn, const char *location, char *name);
 
 /* asynchronous query functions */
 bool		cancel_query(PGconn *conn, int timeout);
-int			wait_connection_availability(PGconn *conn, int timeout);
+int			wait_connection_availability(PGconn *conn, long long timeout);
 
 /* node availability functions */
 bool		is_server_available(const char *conninfo);
-bool		is_server_available_quiet(const char *conninfo);
-bool		is_server_available_params(t_conninfo_param_list *param_list);
-ExecStatusType	connection_ping(PGconn *conn);
-ExecStatusType	connection_ping_reconnect(PGconn *conn);
 
 /* monitoring functions  */
 void
@@ -575,41 +468,43 @@ add_monitoring_record(PGconn *primary_conn,
 					  long long unsigned int apply_lag_bytes
 );
 
-int			get_number_of_monitoring_records_to_delete(PGconn *primary_conn, int keep_history, int node_id);
+int			get_number_of_monitoring_records_to_delete(PGconn *primary_conn, int keep_history);
-bool		delete_monitoring_records(PGconn *primary_conn, int keep_history, int node_id);
+bool		delete_monitoring_records(PGconn *primary_conn, int keep_history);
 
 
 
 /* node voting functions */
-void		initialize_voting_term(PGconn *conn);
+NodeVotingStatus get_voting_status(PGconn *conn);
-int			get_current_term(PGconn *conn);
+VoteRequestResult request_vote(PGconn *conn, t_node_info *this_node, t_node_info *other_node, int electoral_term);
-void		increment_current_term(PGconn *conn);
+int			set_voting_status_initiated(PGconn *conn);
 bool		announce_candidature(PGconn *conn, t_node_info *this_node, t_node_info *other_node, int electoral_term);
 void		notify_follow_primary(PGconn *conn, int primary_node_id);
 bool		get_new_primary(PGconn *conn, int *primary_node_id);
 void		reset_voting_status(PGconn *conn);
 
 /* replication status functions */
-XLogRecPtr	get_primary_current_lsn(PGconn *conn);
+XLogRecPtr	get_current_wal_lsn(PGconn *conn);
-XLogRecPtr	get_node_current_lsn(PGconn *conn);
 XLogRecPtr	get_last_wal_receive_location(PGconn *conn);
-void		init_replication_info(ReplInfo *replication_info);
+bool		get_replication_info(PGconn *conn, ReplInfo *replication_info);
-bool		get_replication_info(PGconn *conn, t_server_type node_type, ReplInfo *replication_info);
 int			get_replication_lag_seconds(PGconn *conn);
-TimeLineID	get_node_timeline(PGconn *conn, char *timeline_id_str);
 void		get_node_replication_stats(PGconn *conn, t_node_info *node_info);
-NodeAttached is_downstream_node_attached(PGconn *conn, char *node_name, char **node_state);
+bool		is_downstream_node_attached(PGconn *conn, char *node_name);
-NodeAttached is_downstream_node_attached_quiet(PGconn *conn, char *node_name, char **node_state);
-void		set_upstream_last_seen(PGconn *conn, int upstream_node_id);
-int			get_upstream_last_seen(PGconn *conn, t_server_type node_type);
 
-bool		is_wal_replay_paused(PGconn *conn, bool check_pending_wal);
+/* BDR functions */
+void		get_all_bdr_node_records(PGconn *conn, BdrNodeInfoList *node_list);
+RecordStatus get_bdr_node_record_by_name(PGconn *conn, const char *node_name, t_bdr_node_info *node_info);
+bool		is_bdr_db(PGconn *conn, PQExpBufferData *output);
+bool		is_active_bdr_node(PGconn *conn, const char *node_name);
+bool		is_bdr_repmgr(PGconn *conn);
+bool		is_table_in_bdr_replication_set(PGconn *conn, const char *tablename, const char *set);
+bool		add_table_to_bdr_replication_set(PGconn *conn, const char *tablename, const char *set);
+void		add_extension_tables_to_bdr_replication_set(PGconn *conn);
 
-/* repmgrd status functions */
+bool		bdr_node_exists(PGconn *conn, const char *node_name);
-CheckStatus	get_repmgrd_status(PGconn *conn);
+ReplSlotStatus get_bdr_node_replication_slot_status(PGconn *conn, const char *node_name);
+void		get_bdr_other_node_name(PGconn *conn, int node_id, char *name_buf);
 
-/* miscellaneous debugging functions */
+bool		am_bdr_failover_handler(PGconn *conn, int node_id);
-const char *print_node_status(NodeStatus node_status);
+void		unset_bdr_failover_handler(PGconn *conn);
-const char *print_pqping_status(PGPing ping_status);
 
 #endif							/* _REPMGR_DBUTILS_H_ */

dirutil.c

@@ -3,7 +3,7 @@
  * dirmod.c
  *	  directory handling functions
  *
- * Copyright (c) EnterpriseDB Corporation, 2010-2021
+ * Copyright (c) 2ndQuadrant, 2010-2017
  *
  * This program is free software: you can redistribute it and/or modify
  * it under the terms of the GNU General Public License as published by
@@ -21,7 +21,6 @@
 
 #include <unistd.h>
 #include <dirent.h>
-#include <signal.h>
 #include <sys/stat.h>
 #include <errno.h>
 #include <stdio.h>
@@ -35,33 +34,34 @@
 #include "dirutil.h"
 #include "strutil.h"
 #include "log.h"
-#include "controldata.h"
 
 static int	unlink_dir_callback(const char *fpath, const struct stat *sb, int typeflag, struct FTW *ftwbuf);
 
-/* PID can be negative if backend is standalone */
-typedef long pgpid_t;
 
 
 /*
- * Check if a directory exists, and if so whether it is empty.
+ * make sure the directory either doesn't exist or is empty
+ * we use this function to check the new data directory and
+ * the directories for tablespaces
  *
- * This function is used for checking both the data directory
+ * This is the same check initdb does on the new PGDATA dir
- * and tablespace directories.
+ *
+ * Returns 0 if nonexistent, 1 if exists and empty, 2 if not empty,
+ * or -1 if trouble accessing directory
  */
-DataDirState
+int
-check_dir(const char *path)
+check_dir(char *path)
 {
-	DIR		   *chkdir = NULL;
+	DIR		   *chkdir;
-	struct dirent *file = NULL;
+	struct dirent *file;
-	int			result = DIR_EMPTY;
+	int			result = 1;
 
 	errno = 0;
 
 	chkdir = opendir(path);
 
 	if (!chkdir)
-		return (errno == ENOENT) ? DIR_NOENT : DIR_ERROR;
+		return (errno == ENOENT) ? 0 : -1;
 
 	while ((file = readdir(chkdir)) != NULL)
 	{
@@ -73,15 +73,25 @@ check_dir(const char *path)
 		}
 		else
 		{
-			result = DIR_NOT_EMPTY;
+			result = 2;			/* not empty */
 			break;
 		}
 	}
 
+#ifdef WIN32
+
+	/*
+	 * This fix is in mingw cvs (runtime/mingwex/dirent.c rev 1.4), but not in
+	 * released version
+	 */
+	if (GetLastError() == ERROR_NO_MORE_FILES)
+		errno = 0;
+#endif
+
 	closedir(chkdir);
 
 	if (errno != 0)
-		return DIR_ERROR;				/* some kind of I/O error? */
+		return -1;				/* some kind of I/O error? */
 
 	return result;
 }
@@ -91,77 +101,25 @@ check_dir(const char *path)
  * Create directory with error log message when failing
  */
 bool
-create_dir(const char *path)
+create_dir(char *path)
 {
-	char create_dir_path[MAXPGPATH];
+	if (mkdir_p(path, 0700) == 0)
-
-	/* mkdir_p() may modify the supplied path */
-	strncpy(create_dir_path, path, MAXPGPATH);
-
-	if (mkdir_p(create_dir_path, 0700) == 0)
 		return true;
 
-	log_error(_("unable to create directory \"%s\""), create_dir_path);
+	log_error(_("unable to create directory \"%s\": %s"),
-	log_detail("%s", strerror(errno));
+			  path, strerror(errno));
 
 	return false;
 }
 
-
 bool
-set_dir_permissions(const char *path, int server_version_num)
+set_dir_permissions(char *path)
 {
-	struct stat stat_buf;
+	return (chmod(path, 0700) != 0) ? false : true;
-	bool no_group_access =
-		(server_version_num != UNKNOWN_SERVER_VERSION_NUM) &&
-		(server_version_num < 110000);
-	/*
-	 * At this point the path should exist, so this check is very
-	 * much just-in-case.
-	 */
-	if (stat(path, &stat_buf) != 0)
-	{
-		if (errno == ENOENT)
-		{
-			log_warning(_("directory \"%s\" does not exist"), path);
-		}
-		else
-		{
-			log_warning(_("could not read permissions of directory \"%s\""),
-						path);
-			log_detail("%s", strerror(errno));
-		}
-
-		return false;
-	}
-
-	/*
-	 * If mode is not 0700 or 0750, attempt to change.
-	 */
-	if ((no_group_access == true  && (stat_buf.st_mode & (S_IRWXG | S_IRWXO)))
-	 || (no_group_access == false && (stat_buf.st_mode & (S_IWGRP | S_IRWXO))))
-	{
-		/*
-		 * Currently we default to 0700.
-		 * There is no facility to override this directly,
-		 * but the user can manually create the directory with
-		 * the desired permissions.
-		 */
-
-		if (chmod(path, 0700) != 0) {
-			log_error(_("unable to change permissions of directory \"%s\""), path);
-			log_detail("%s", strerror(errno));
-			return false;
-		}
-
-		return true;
-	}
-
-	/* Leave as-is */
-	return true;
 }
 
 
+
 /* function from initdb.c */
 /* source adapted from FreeBSD /src/bin/mkdir/mkdir.c */
 
@@ -188,6 +146,26 @@ mkdir_p(char *path, mode_t omode)
 	oumask = 0;
 	retval = 0;
 
+#ifdef WIN32
+	/* skip network and drive specifiers for win32 */
+	if (strlen(p) >= 2)
+	{
+		if (p[0] == '/' && p[1] == '/')
+		{
+			/* network drive */
+			p = strstr(p + 2, "/");
+			if (p == NULL)
+				return 1;
+		}
+		else if (p[1] == ':' &&
+				 ((p[0] >= 'a' && p[0] <= 'z') ||
+				  (p[0] >= 'A' && p[0] <= 'Z')))
+		{
+			/* local drive */
+			p += 2;
+		}
+	}
+#endif
 
 	if (p[0] == '/')			/* Skip leading '/'. */
 		++p;
@@ -205,7 +183,7 @@ mkdir_p(char *path, mode_t omode)
 			/*
 			 * POSIX 1003.2: For each dir operand that does not name an
 			 * existing directory, effects equivalent to those caused by the
-			 * following command shall occur:
+			 * following command shall occcur:
 			 *
 			 * mkdir -p -m $(umask -S),u+wx $(dirname dir) && mkdir [-m mode]
 			 * dir
@@ -249,9 +227,9 @@ mkdir_p(char *path, mode_t omode)
 
 
 bool
-is_pg_dir(const char *path)
+is_pg_dir(char *path)
 {
-	char		dirpath[MAXPGPATH] = "";
+	char		dirpath[MAXPGPATH];
 	struct stat sb;
 
 	/* test pgdata */
@@ -264,93 +242,17 @@ is_pg_dir(const char *path)
 	return false;
 }
 
-/*
- * Attempt to determine if a PostgreSQL data directory is in use
- * by reading the pidfile. This is the same mechanism used by
- * "pg_ctl".
- *
- * This function will abort with appropriate log messages if a file error
- * is encountered, as the user will need to address the situation before
- * any further useful progress can be made.
- */
-PgDirState
-is_pg_running(const char *path)
-{
-	long		pid;
-	FILE	   *pidf;
-
-	char pid_file[MAXPGPATH];
-
-	/* it's reasonable to assume the pidfile name will not change */
-	snprintf(pid_file, MAXPGPATH, "%s/postmaster.pid", path);
-
-	pidf = fopen(pid_file, "r");
-	if (pidf == NULL)
-	{
-		/*
-		 * No PID file - PostgreSQL shouldn't be running. From 9.3 (the
-		 * earliest version we care about) removal of the PID file will
-		 * cause the postmaster to shut down, so it's highly unlikely
-		 * that PostgreSQL will still be running.
-		 */
-		if (errno == ENOENT)
-		{
-			return PG_DIR_NOT_RUNNING;
-		}
-		else
-		{
-			log_error(_("unable to open PostgreSQL PID file \"%s\""), pid_file);
-			log_detail("%s", strerror(errno));
-			exit(ERR_BAD_CONFIG);
-		}
-	}
-
-
-	/*
-	 * In the unlikely event we're unable to extract a PID from the PID file,
-	 * log a warning but assume we're not dealing with a running instance
-	 * as PostgreSQL should have shut itself down in these cases anyway.
-	 */
-	if (fscanf(pidf, "%ld", &pid) != 1)
-	{
-		/* Is the file empty? */
-		if (ftell(pidf) == 0 && feof(pidf))
-		{
-			log_warning(_("PostgreSQL PID file \"%s\" is empty"), path);
-		}
-		else
-		{
-			log_warning(_("invalid data in PostgreSQL PID file \"%s\""), path);
-		}
-
-		fclose(pidf);
-
-		return PG_DIR_NOT_RUNNING;
-	}
-
-	fclose(pidf);
-
-	if (pid == getpid())
-		return PG_DIR_NOT_RUNNING;
-
-	if (pid == getppid())
-		return PG_DIR_NOT_RUNNING;
-
-	if (kill(pid, 0) == 0)
-		return PG_DIR_RUNNING;
-
-	return PG_DIR_NOT_RUNNING;
-}
-
 
 bool
-create_pg_dir(const char *path, bool force)
+create_pg_dir(char *path, bool force)
 {
-	/* Check this directory can be used as a PGDATA dir */
+	bool		pg_dir = false;
+
+	/* Check this directory could be used as a PGDATA dir */
 	switch (check_dir(path))
 	{
-		case DIR_NOENT:
+		case 0:
-			/* Directory does not exist, attempt to create it. */
+			/* dir not there, must create it */
 			log_info(_("creating directory \"%s\"..."), path);
 
 			if (!create_dir(path))
@@ -360,90 +262,55 @@ create_pg_dir(const char *path, bool force)
 				return false;
 			}
 			break;
-		case DIR_EMPTY:
+		case 1:
-			/*
+			/* Present but empty, fix permissions and use it */
-			 * Directory exists but empty, fix permissions and use it.
+			log_info(_("checking and correcting permissions on existing directory %s"),
-			 *
-			 * Note that at this point the caller might not know the server
-			 * version number, so in this case "set_dir_permissions()" will
-			 * accept 0750 as a valid setting. As this is invalid in Pg10 and
-			 * earlier,  the caller should call "set_dir_permissions()" again
-			 * when it has the number.
-			 *
-			 * We need to do the permissions check here in any case to catch
-			 * fatal permissions early.
-			 */
-			log_info(_("checking and correcting permissions on existing directory \"%s\""),
 					 path);
 
-			if (!set_dir_permissions(path, UNKNOWN_SERVER_VERSION_NUM))
+			if (!set_dir_permissions(path))
 			{
+				log_error(_("unable to change permissions of directory \"%s\":\n  %s"),
+						  path, strerror(errno));
 				return false;
 			}
 			break;
-		case DIR_NOT_EMPTY:
+		case 2:
-			/* exists but is not empty */
+			/* Present and not empty */
 			log_warning(_("directory \"%s\" exists but is not empty"),
 						path);
 
-			if (is_pg_dir(path))
+			pg_dir = is_pg_dir(path);
+
+			if (pg_dir && force)
 			{
-				if (force == true)
+				/* TODO: check DB state, if not running overwrite */
+
+				if (false)
 				{
-					log_notice(_("-F/--force provided - deleting existing data directory \"%s\""), path);
+					log_notice(_("deleting existing data directory \"%s\""), path);
 					nftw(path, unlink_dir_callback, 64, FTW_DEPTH | FTW_PHYS);
-
-					/* recreate the directory ourselves to ensure permissions are correct */
-					if (!create_dir(path))
-					{
-						log_error(_("unable to create directory \"%s\"..."),
-								  path);
-						return false;
-					}
-
-					return true;
 				}
-
+				/* Let it continue */
+				break;
+			}
+			else if (pg_dir && !force)
+			{
+				log_hint(_("This looks like a PostgreSQL directory.\n"
+						   "If you are sure you want to clone here, "
+						   "please check there is no PostgreSQL server "
+						   "running and use the -F/--force option"));
 				return false;
 			}
-			else
-			{
-				if (force == true)
-				{
-					log_notice(_("deleting existing directory \"%s\""), path);
-					nftw(path, unlink_dir_callback, 64, FTW_DEPTH | FTW_PHYS);
 
-					/* recreate the directory ourselves to ensure permissions are correct */
+			return false;
-					if (!create_dir(path))
+		default:
-					{
+			log_error(_("could not access directory \"%s\": %s"),
-						log_error(_("unable to create directory \"%s\"..."),
+					  path, strerror(errno));
-								  path);
-						return false;
-					}
-
-					return true;
-				}
-				return false;
-			}
-			break;
-		case DIR_ERROR:
-			log_error(_("could not access directory \"%s\"")
-					  , path);
-			log_detail("%s", strerror(errno));
 			return false;
 	}
-
 	return true;
 }
 
-
-
-int
-rmdir_recursive(const char *path)
-{
-	return nftw(path, unlink_dir_callback, 64, FTW_DEPTH | FTW_PHYS);
-}
-
 static int
 unlink_dir_callback(const char *fpath, const struct stat *sb, int typeflag, struct FTW *ftwbuf)
 {

dirutil.h

@@ -1,6 +1,6 @@
 /*
  * dirutil.h
- * Copyright (c) EnterpriseDB Corporation, 2010-2021
+ * Copyright (c) 2ndQuadrant, 2010-2017
  *
  * This program is free software: you can redistribute it and/or modify
  * it under the terms of the GNU General Public License as published by
@@ -19,29 +19,12 @@
 #ifndef _DIRUTIL_H_
 #define _DIRUTIL_H_
 
-typedef enum
-{
-	DIR_ERROR = -1,
-	DIR_NOENT,
-	DIR_EMPTY,
-	DIR_NOT_EMPTY
-} DataDirState;
-
-typedef enum
-{
-	PG_DIR_ERROR = -1,
-	PG_DIR_NOT_RUNNING,
-	PG_DIR_RUNNING
-} PgDirState;
-
 extern int	mkdir_p(char *path, mode_t omode);
-extern bool set_dir_permissions(const char *path, int server_version_num);
+extern bool set_dir_permissions(char *path);
 
-extern DataDirState	check_dir(const char *path);
+extern int	check_dir(char *path);
-extern bool create_dir(const char *path);
+extern bool create_dir(char *path);
-extern bool is_pg_dir(const char *path);
+extern bool is_pg_dir(char *path);
-extern PgDirState is_pg_running(const char *path);
+extern bool create_pg_dir(char *path, bool force);
-extern bool create_pg_dir(const char *path, bool force);
-extern int rmdir_recursive(const char *path);
 
 #endif

doc/.gitignore

@@ -1,9 +0,0 @@
-HTML.index
-bookindex.xml
-html-stamp
-html/
-repmgr.html
-version.xml
-*.fo
-*.pdf
-*.sgml

doc/Makefile

@@ -1,104 +0,0 @@
-# Make "html" the default target, since that is what most people tend
-# to want to use.
-html:
-
-all: html
-
-subdir = doc
-repmgr_top_builddir = ..
-include $(repmgr_top_builddir)/Makefile.global
-
-XMLINCLUDE = --path .
-
-ifndef XMLLINT
-XMLLINT = $(missing) xmllint
-endif
-
-ifndef XSLTPROC
-XSLTPROC = $(missing) xsltproc
-endif
-
-ifndef FOP
-FOP = $(missing) fop
-endif
-
-override XSLTPROCFLAGS += --stringparam repmgr.version '$(REPMGR_VERSION)'
-
-GENERATED_XML = version.xml
-ALLXML := $(wildcard $(srcdir)/*.xml) $(GENERATED_XML)
-
-
-version.xml: $(repmgr_top_builddir)/repmgr_version.h
-	{ \
-	  echo "<!ENTITY repmgrversion \"$(REPMGR_VERSION)\">"; \
-	  echo "<!ENTITY releasedate \"$(REPMGR_RELEASE_DATE)\">"; \
-	} > $@
-
-##
-## HTML
-##
-
-
-html: html-stamp
-
-html-stamp: stylesheet.xsl repmgr.xml $(ALLXML)
-	$(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^)
-	$(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) $(XSLTPROC_HTML_FLAGS) $(wordlist 1,2,$^)
-	cp $(srcdir)/stylesheet.css  $(srcdir)/website-docs.css html/
-	touch $@
-
-# single-page HTML
-repmgr.html: stylesheet-html-nochunk.xsl repmgr.xml $(ALLXML)
-	$(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^)
-	$(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) $(XSLTPROC_HTML_FLAGS) -o $@ $(wordlist 1,2,$^)
-
-
-zip: html
-	cp -r html repmgr-docs-$(REPMGR_VERSION)
-	zip -r repmgr-docs-$(REPMGR_VERSION).zip repmgr-docs-$(REPMGR_VERSION)
-	rm -rf repmgr-docs-$(REPMGR_VERSION)
-
-##
-## Print
-##
-
-repmgr.pdf:
-	$(error Invalid target; use repmgr-A4.pdf or repmgr-US.pdf as targets)
-
-# Standard paper size
-
-repmgr-A4.fo: stylesheet-fo.xsl repmgr.xml $(ALLXML)
-	$(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^)
-	$(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) --stringparam paper.type A4 -o $@ $(wordlist 1,2,$^)
-
-repmgr-A4.pdf: repmgr-A4.fo
-	$(FOP) -fo $< -pdf $@
-
-# North American paper size
-
-repmgr-US.fo: stylesheet-fo.xsl repmgr.xml $(ALLXML)
-	$(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^)
-	$(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) --stringparam paper.type USletter -o $@ $(wordlist 1,2,$^)
-
-repmgr-US.pdf: repmgr-US.fo
-	$(FOP) -fo $< -pdf $@
-
-
-install: html
-	@$(MKDIR_P) $(DESTDIR)$(docdir)/$(docmoduledir)/repmgr
-	@$(INSTALL_DATA) $(wildcard html/*.html) $(wildcard html/*.css) $(DESTDIR)$(docdir)/$(docmoduledir)/repmgr
-	@echo Installed docs to $(DESTDIR)$(docdir)/$(docmoduledir)/repmgr
-
-clean:
-	rm -f html-stamp
-	rm -f HTML.index $(GENERATED_XML)
-	rm -f repmgr.html
-	rm -f repmgr-A4.pdf
-	rm -f repmgr-US.pdf
-	rm -f *.fo
-	rm -f html/*
-
-maintainer-clean:
-	rm -rf html
-
-.PHONY: html

doc/appendix-faq.xml

@@ -1,488 +0,0 @@
-<appendix id="appendix-faq" xreflabel="FAQ">
-
-  <title>FAQ (Frequently Asked Questions)</title>
-
-  <indexterm>
-    <primary>FAQ (Frequently Asked Questions)</primary>
-  </indexterm>
-
-  <sect1 id="faq-general" xreflabel="General">
-    <title>General</title>
-
-    <sect2 id="faq-xrepmgr-version-diff" xreflabel="Version differences">
-      <title>What's the difference between the repmgr versions?</title>
-      <para>
-        &repmgr; 4 is a complete rewrite of the previous &repmgr; code base
-        and implements &repmgr; as a PostgreSQL extension. It
-        supports all PostgreSQL versions from 9.3 (although some &repmgr;
-        features are not available for PostgreSQL 9.3 and 9.4).
-      </para>
-      <note>
-        <para>
-          &repmgr; 5 is fundamentally the same code base as &repmgr; 4, but provides
-          support for the revised replication configuration mechanism in PostgreSQL 12.
-        </para>
-        <para>
-          Support for PostgreSQL 9.3 is no longer available from &repmgr; 5.2.
-        </para>
-      </note>
-      <para>
-        &repmgr; 3.x builds on the improved replication facilities added
-        in PostgreSQL 9.3, as well as improved automated failover support
-        via &repmgrd;, and is not compatible with PostgreSQL 9.2
-        and earlier. We recommend upgrading to &repmgr; 4, as the &repmgr; 3.x
-        series is no longer maintained.
-      </para>
-      <para>
-        &repmgr; 2.x supports PostgreSQL 9.0 ~ 9.3. While it is compatible
-        with PostgreSQL 9.3, we recommend using repmgr 4.x. &repmgr; 2.x is
-        no longer maintained.
-      </para>
-      <para>
-        See also <link linkend="install-compatibility-matrix">&repmgr; compatibility matrix</link>
-        and <link linkend="faq-upgrade-repmgr">Should I upgrade &repmgr;?</link>.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-replication-slots-advantage" xreflabel="Advantages of replication slots">
-      <title>What's the advantage of using replication slots?</title>
-      <para>
-        Replication slots, introduced in PostgreSQL 9.4, ensure that the
-        primary server will retain WAL files until they have been consumed
-        by all standby servers. This means standby servers should never
-        fail due to not being able to retrieve required WAL files from the
-        primary.
-      </para>
-      <para>
-        However this does mean that if a standby is no longer connected to the
-        primary, the presence of the replication slot will cause WAL files
-        to be retained indefinitely, and eventually lead to disk space
-        exhaustion.
-      </para>
-
-      <tip>
-        <para>
-          Our recommended configuration is to configure
-          <ulink url="https://www.pgbarman.org/">Barman</ulink> as a fallback
-          source of WAL files, rather than maintain replication slots for
-          each standby. See also: <link linkend="cloning-from-barman-restore-command">Using Barman as a WAL file source</link>.
-        </para>
-      </tip>
-    </sect2>
-
-    <sect2 id="faq-replication-slots-number" xreflabel="Number of replication slots">
-      <title>How many replication slots should I define in <varname>max_replication_slots</varname>?</title>
-      <para>
-        Normally at least same number as the number of standbys which will connect
-        to the node. Note that changes to <varname>max_replication_slots</varname> require a server
-        restart to take effect, and as there is no particular penalty for unused
-        replication slots, setting a higher figure will make adding new nodes
-        easier.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-hash-index" xreflabel="Hash indexes">
-      <title>Does &repmgr; support hash indexes?</title>
-      <para>
-        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
-        <ulink url="https://www.postgresql.org/docs/9.6/sql-createindex.html#AEN80279">PostgreSQL documentation</ulink>
-        for details.
-      </para>
-      <para>
-        From PostgreSQL 10, this restriction has been lifted and hash indexes can be used
-        in a streaming replication cluster.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-upgrades" xreflabel="Upgrading PostgreSQL with repmgr">
-      <title>Can &repmgr; assist with upgrading a PostgreSQL cluster?</title>
-      <para>
-        For <emphasis>minor</emphasis> version upgrades, e.g. from 9.6.7 to 9.6.8, a common
-        approach is to upgrade a standby to the latest version, perform a
-        <link linkend="performing-switchover">switchover</link> promoting it to a primary,
-        then upgrade the former primary.
-      </para>
-      <para>
-        For <emphasis>major</emphasis> 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 <ulink url="https://www.postgresql.org/docs/current/pgupgrade.html">pg_upgrade</ulink>
-        and recloning standbys from this.
-      </para>
-      <para>
-        To minimize downtime during major upgrades from PostgreSQL 9.4 and later,
-        <ulink url="https://www.2ndquadrant.com/en/resources/pglogical/">pglogical</ulink>
-        can be used to set up a parallel cluster using the newer PostgreSQL version,
-        which can be kept in sync with the existing production cluster until the
-        new cluster is ready to be put into production.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-libdir-repmgr-error">
-      <title>What does this error mean: <literal>ERROR: could not access file "$libdir/repmgr"</literal>?</title>
-      <para>
-        It means the &repmgr; extension code is not installed in the
-        PostgreSQL application directory. This typically happens when using PostgreSQL
-        packages provided by a third-party vendor, which often have different
-        filesystem layouts.
-      </para>
-      <para>
-        Either use PostgreSQL packages provided by the community or EnterpriseDB; if this
-        is not possible, contact your vendor for assistance.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-old-packages">
-      <title>How can I obtain old versions of &repmgr; packages?</title>
-      <para>
-        See appendix <xref linkend="packages-old-versions"/> for details.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-required-for-replication">
-      <title>Is &repmgr; required for streaming replication?</title>
-      <para>
-        No.
-      </para>
-      <para>
-        &repmgr; (together with &repmgrd;) assists with
-        <emphasis>managing</emphasis> replication. It does not actually perform replication, which
-        is part of the core PostgreSQL functionality.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-what-if-repmgr-uninstalled">
-      <title>Will replication stop working if &repmgr; is uninstalled?</title>
-      <para>
-        No. See preceding question.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-version-mix">
-      <title>Does it matter if different &repmgr; versions are present in the replication cluster?</title>
-      <para>
-        Yes. If different &quot;major&quot; &repmgr; versions (e.g. 3.3.x and 4.1.x) are present,
-        &repmgr; (in particular &repmgrd;)
-        may not run, or run properly, or in the worst case (if different &repmgrd;
-        versions are running and there are differences in the failover implementation) break
-        your replication cluster.
-      </para>
-      <para>
-        If different &quot;minor&quot; &repmgr; versions (e.g. 4.1.1 and 4.1.6) are installed,
-        &repmgr; will function, but we strongly recommend always running the same version
-        to ensure there are no unexpected surprises, e.g. a newer version behaving slightly
-        differently to the older version.
-      </para>
-      <para>
-        See also <link linkend="faq-upgrade-repmgr">Should I upgrade &repmgr;?</link>.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-upgrade-repmgr">
-      <title>Should I upgrade &repmgr;?</title>
-      <para>
-        Yes.
-      </para>
-      <para>
-        We don't release new versions for fun, you know. Upgrading may require a little effort,
-        but running an older &repmgr; version with bugs which have since been fixed may end up
-        costing you more effort. The same applies to PostgreSQL itself.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-conf-data-directory">
-      <title>Why do I need to specify the data directory location in repmgr.conf?</title>
-      <para>
-        In some circumstances &repmgr; may need to access a PostgreSQL data
-        directory while the PostgreSQL server is not running, e.g. to confirm
-        it shut down cleanly during a <link linkend="performing-switchover">switchover</link>.
-      </para>
-      <para>
-        Additionally, this provides support when using &repmgr; on PostgreSQL 9.6 and
-        earlier, where the <literal>repmgr</literal> user is not a superuser; in that
-        case the <literal>repmgr</literal> user will not be able to access the
-        <literal>data_directory</literal> configuration setting, access to which is restricted
-        to superusers.
-      </para>
-      <para>
-        In PostgreSQL 10 and later, non-superusers can be added to the
-        <ulink url="https://www.postgresql.org/docs/current/default-roles.html">default role</ulink>
-        <option>pg_read_all_settings</option> (or the meta-role <option>pg_monitor</option>)
-        which will enable them to read this setting.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-third-party-packages" xreflabel="Compatibility with third party vendor packages">
-      <title>Are &repmgr; packages compatible with <literal>$third_party_vendor</literal>'s packages?</title>
-      <para>
-        &repmgr; packages provided by EnterpriseDB are compatible with the community-provided PostgreSQL
-        packages and specified software provided by EnterpriseDB.
-      </para>
-      <para>
-        A number of other vendors provide their own versions of PostgreSQL packages, often with different
-        package naming schemes and/or file locations.
-      </para>
-      <para>
-        We cannot guarantee that &repmgr; packages will be compatible with these packages.
-        It may be possible to override package dependencies (e.g. <literal>rpm --nodeps</literal>
-        for CentOS-based systems or <literal>dpkg --force-depends</literal> for Debian-based systems).
-      </para>
-    </sect2>
-  </sect1>
-
-  <sect1 id="faq-repmgr" xreflabel="repmgr">
-    <title><command>repmgr</command></title>
-
-    <sect2 id="faq-register-existing-node" xreflabel="registering an existing node">
-      <title>Can I register an existing PostgreSQL server with repmgr?</title>
-      <para>
-        Yes, any existing PostgreSQL server which is part of the same replication
-        cluster can be registered with &repmgr;. There's no requirement for a
-        standby to have been cloned using &repmgr;.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-clone-other-source" >
-      <title>Can I use a standby not cloned by &repmgr; as a &repmgr; node?</title>
-
-      <para>
-        For a standby which has been manually cloned or recovered from an external
-        backup manager such as Barman, the command
-        <command><link linkend="repmgr-standby-clone">repmgr standby clone --replication-conf-only</link></command>
-        can be used to create the correct replication configuration file for
-        use with &repmgr; (and will create a replication slot if required). Once this has been done,
-        <link linkend="repmgr-standby-register">register the node</link> as usual.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-recovery-conf" >
-      <title>What does &repmgr; write in the replication configuration, and what options can be set there?</title>
-      <para>
-        See section <link linkend="repmgr-standby-clone-recovery-conf">Customising replication configuration</link>.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-failed-primary-standby" xreflabel="Reintegrate a failed primary as a standby">
-      <title>How can a failed primary be re-added as a standby?</title>
-      <para>
-        This is a two-stage process. First, the failed primary's data directory
-        must be re-synced with the current primary; secondly the failed primary
-        needs to be re-registered as a standby.
-      </para>
-      <para>
-        It's possible to use <command>pg_rewind</command> to re-synchronise the existing data
-        directory, which will usually be much
-        faster than re-cloning the server. However <command>pg_rewind</command> can only
-        be used if PostgreSQL either has <varname>wal_log_hints</varname> enabled, or
-        data checksums were enabled when the cluster was initialized.
-      </para>
-      <para>
-        Note that <command>pg_rewind</command> is available as part of the core PostgreSQL
-        distribution from PostgreSQL 9.5, and as a third-party utility for PostgreSQL 9.3 and 9.4.
-      </para>
-      <para>
-        &repmgr; provides the command <command>repmgr node rejoin</command> which can
-        optionally execute <command>pg_rewind</command>; see the <xref linkend="repmgr-node-rejoin"/>
-        documentation for details, in particular the section <xref linkend="repmgr-node-rejoin-pg-rewind"/>.
-      </para>
-      <para>
-        If <command>pg_rewind</command> cannot be used, then the data directory will need
-        to be re-cloned from scratch.
-      </para>
-
-    </sect2>
-
-    <sect2 id="faq-repmgr-check-configuration" xreflabel="Check PostgreSQL configuration">
-      <title>Is there an easy way to check my primary server is correctly configured for use with &repmgr;?</title>
-      <para>
-        Execute <command><link linkend="repmgr-standby-clone">repmgr standby clone</link></command>
-        with the <literal>--dry-run</literal> option; this will report any configuration problems
-        which need to be rectified.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-clone-skip-config-files" xreflabel="">
-      <title>When cloning a standby, how can I get &repmgr; to copy
-        <filename>postgresql.conf</filename> and <filename>pg_hba.conf</filename> from the PostgreSQL configuration
-        directory in <filename>/etc</filename>?</title>
-      <para>
-        Use the command line option <literal>--copy-external-config-files</literal>. For more details
-        see <xref linkend="repmgr-standby-clone-config-file-copying"/>.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-shared-preload-libraries-no-repmgrd" xreflabel="shared_preload_libraries without repmgrd">
-      <title>Do I need to include <literal>shared_preload_libraries = 'repmgr'</literal>
-        in <filename>postgresql.conf</filename> if I'm not using &repmgrd;?</title>
-      <para>
-        No, the <literal>repmgr</literal> shared library is only needed when running &repmgrd;.
-        If you later decide to run &repmgrd;, you just need to add
-        <literal>shared_preload_libraries = 'repmgr'</literal> and restart PostgreSQL.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-permissions" xreflabel="Replication permission problems">
-      <title>I've provided replication permission for the <literal>repmgr</literal> user in <filename>pg_hba.conf</filename>
-        but <command>repmgr</command>/&repmgrd; complains it can't connect to the server... Why?</title>
-      <para>
-        <command>repmgr</command> and &repmgrd; need to be able to connect to the repmgr database
-        with a normal connection to query metadata. The <literal>replication</literal> connection
-        permission is for PostgreSQL's streaming replication (and doesn't  necessarily need to be the <literal>repmgr</literal> user).
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-clone-provide-primary-conninfo" xreflabel="Providing primary connection parameters">
-      <title>When cloning a standby, why do I need to provide the connection parameters
-        for the primary server on the command line, not in the configuration file?</title>
-      <para>
-        Cloning a standby is a one-time action; the role of the server being cloned
-        from could change, so fixing it in the configuration file would create
-        confusion. If &repmgr; needs to establish a connection to the primary
-        server, it can retrieve this from the <literal>repmgr.nodes</literal> table on the local
-        node, and if necessary scan the replication cluster until it locates the active primary.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-clone-waldir-xlogdir" xreflabel="Providing a custom WAL directory">
-      <title>When cloning a standby, how do I ensure the WAL files are placed in a custom directory?</title>
-      <para>
-        Provide the option <literal>--waldir</literal>  (<literal>--xlogdir</literal> in PostgreSQL 9.6
-        and earlier) with the absolute path to the WAL directory in <varname>pg_basebackup_options</varname>.
-        For more details see <xref linkend="cloning-advanced-pg-basebackup-options"/>.
-      </para>
-      <para>
-        In &repmgr; 5.2 and later, this setting will also be honoured when cloning from Barman.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-events-no-fkey" xreflabel="No foreign key on node_id in repmgr.events">
-      <title>Why is there no foreign key on the <literal>node_id</literal> column in the <literal>repmgr.events</literal>
-        table?</title>
-      <para>
-        Under some circumstances event notifications can be generated for servers
-        which have not yet been registered; it's also useful to retain a record
-        of events which includes servers removed from the replication cluster
-        which no longer have an entry in the <literal>repmgr.nodes</literal> table.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-recovery-conf-quoted-values" xreflabel="Quoted values in replication.conf">
-      <title>Why are some values in <filename>recovery.conf</filename> (PostgreSQL 11 and earlier) surrounded by pairs of single quotes?</title>
-      <para>
-        This is to ensure that user-supplied values which are written as parameter values in <filename>recovery.conf</filename>
-        are escaped correctly and do not cause errors when the file is parsed.
-      </para>
-      <para>
-        The escaping is performed by an internal PostgreSQL routine, which leaves strings consisting
-        of digits and alphabetical characters only as-is, but wraps everything else in pairs of single quotes,
-        even if the string does not contain any characters which need escaping.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgr-exclude-metadata-from-dump" xreflabel="Excluding repmgr metadata from pg_dump output">
-      <title>How can I exclude &repmgr; metadata from <application>pg_dump</application> output?</title>
-      <para>
-        Beginning with &repmgr; 5.2, the metadata tables associated with the &repmgr; extension
-        (<literal>repmgr.nodes</literal>, <literal>repmgr.events</literal> and <literal>repmgr.monitoring_history</literal>)
-        have been marked as dumpable as they contain configuration and user-generated data.
-      </para>
-      <para>
-        To exclude these from <application>pg_dump</application> output, add the flag <option>--exclude-schema=repmgr</option>.
-      </para>
-      <para>
-        To exclude individual &repmgr; metadata tables from <application>pg_dump</application> output, add the flag
-        e.g. <option>--exclude-table=repmgr.monitoring_history</option>. This flag can be provided multiple times
-        to exclude individual tables,
-      </para>
-    </sect2>
-
-  </sect1>
-
-  <sect1 id="faq-repmgrd" xreflabel="repmgrd">
-    <title>&repmgrd;</title>
-
-
-    <sect2 id="faq-repmgrd-prevent-promotion" xreflabel="Prevent standby from being promoted to primary">
-      <title>How can I prevent a node from ever being promoted to primary?</title>
-      <para>
-        In <filename>repmgr.conf</filename>, set its priority to a value of <literal>0</literal>; apply the changed setting with
-        <command><link linkend="repmgr-standby-register">repmgr standby register --force</link></command>.
-      </para>
-      <para>
-        Additionally, if <varname>failover</varname> is set to <literal>manual</literal>, the node will never
-        be considered as a promotion candidate.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgrd-delayed-standby" xreflabel="Delayed standby support">
-      <title>Does &repmgrd; support delayed standbys?</title>
-      <para>
-        &repmgrd; can monitor delayed standbys - those set up with
-        <varname>recovery_min_apply_delay</varname> set to a non-zero value
-        in the replication configuration. However &repmgrd; does not currently
-        consider this setting, and therefore may not be able to properly evaluate
-        the node as a promotion candidate.
-      </para>
-      <para>
-        We recommend that delayed standbys are explicitly excluded from promotion
-        by setting <varname>priority</varname> to <literal>0</literal> in
-        <filename>repmgr.conf</filename>.
-      </para>
-      <para>
-        Note that after registering a delayed standby, &repmgrd; will only start
-        once the metadata added in the primary node has been replicated.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgrd-logfile-rotate" xreflabel="repmgrd logfile rotation">
-      <title>How can I get &repmgrd; to rotate its logfile?</title>
-      <para>
-        Configure your system's <literal>logrotate</literal> service to do this; see <xref linkend="repmgrd-log-rotation"/>.
-      </para>
-
-    </sect2>
-
-    <sect2 id="faq-repmgrd-recloned-no-start" xreflabel="repmgrd not restarting after node cloned">
-      <title>I've recloned a failed primary as a standby, but &repmgrd; refuses to start?</title>
-      <para>
-        Check you registered the standby after recloning. If unregistered, the standby
-        cannot be considered as a promotion candidate even if <varname>failover</varname> is set to
-        <literal>automatic</literal>, which is probably not what you want. &repmgrd; will start if
-        <varname>failover</varname> is set to <literal>manual</literal> so the node's replication status can still
-        be monitored, if desired.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgrd-pg-bindir" xreflabel="repmgrd does not apply pg_bindir to promote_command or follow_command">
-      <title>
-        &repmgrd; ignores pg_bindir when executing <varname>promote_command</varname> or <varname>follow_command</varname>
-      </title>
-      <para>
-        <varname>promote_command</varname> or <varname>follow_command</varname> can be user-defined scripts,
-        so &repmgr; will not apply <option>pg_bindir</option> even if executing &repmgr;. Always provide the full
-        path; see <xref linkend="repmgrd-automatic-failover-configuration"/> for more details.
-      </para>
-    </sect2>
-
-    <sect2 id="faq-repmgrd-startup-no-upstream" xreflabel="repmgrd does not start if upstream node is not running">
-      <title>
-        &repmgrd; aborts startup with the error "<literal>upstream node must be running before repmgrd can start</literal>"
-      </title>
-      <para>
-        &repmgrd; does this to avoid starting up on a replication cluster
-        which is not in a healthy state. If the upstream is unavailable, &repmgrd;
-        may initiate a failover immediately after starting up, which could have unintended side-effects,
-        particularly if &repmgrd; is not running on other nodes.
-      </para>
-      <para>
-        In particular, it's possible that the node's local copy of the <literal>repmgr.nodes</literal> copy
-        is out-of-date, which may lead to incorrect failover behaviour.
-      </para>
-      <para>
-        The onus is therefore on the administrator to manually set the cluster to a stable, healthy state before
-        starting &repmgrd;.
-      </para>
-    </sect2>
-
-  </sect1>
-</appendix>

doc/appendix-packages.xml

@@ -1,542 +0,0 @@
-<appendix id="appendix-packages" xreflabel="Package details">
-
-  <title>&repmgr; package details</title>
-
-  <indexterm>
-    <primary>packages</primary>
-  </indexterm>
-
-  <para>
-    This section provides technical details about various &repmgr; binary
-    packages, such as location of the installed binaries and
-    configuration files.
-  </para>
-
-  <sect1 id="packages-centos" xreflabel="CentOS packages">
-    <title>CentOS Packages</title>
-
-    <indexterm>
-      <primary>packages</primary>
-      <secondary>CentOS packages</secondary>
-    </indexterm>
-
-    <indexterm>
-      <primary>CentOS</primary>
-      <secondary>package information</secondary>
-    </indexterm>
-
-    <para>
-      Currently, &repmgr; RPM packages are provided for versions 6.x and 7.x of CentOS. These should also
-      work on matching versions of Red Hat Enterprise Linux, Scientific Linux and Oracle Enterprise Linux;
-      together with CentOS, these are the same RedHat-based distributions for which the main community project
-      (PGDG) provides packages (see the <ulink url="https://yum.postgresql.org/">PostgreSQL RPM Building Project</ulink>
-      page for details).
-    </para>
-
-    <para>
-      Note these &repmgr; RPM packages are not designed to work with SuSE/OpenSuSE.
-    </para>
-
-    <note>
-      <para>
-        &repmgr; packages are designed to be compatible with community-provided PostgreSQL packages.
-        They may not work with vendor-specific packages such as those provided by RedHat for RHEL
-        customers, as the filesystem layout may be different to the community RPMs.
-        Please contact your support vendor for assistance.
-      </para>
-    </note>
-
-    <sect2 id="packages-centos-repositories">
-      <title>CentOS repositories</title>
-
-      <para>
-        &repmgr; packages are available from the public EDB repository, and also the
-        PostgreSQL community repository. The EDB repository is updated immediately
-        after each &repmgr; release.
-      </para>
-
-      <table id="centos-2ndquadrant-repository">
-        <title>EDB public repository</title>
-        <tgroup cols="2">
-          <tbody>
-            <row>
-              <entry>Repository URL:</entry>
-              <entry><ulink url="https://dl.enterprisedb.com/">https://dl.enterprisedb.com/</ulink></entry>
-            </row>
-            <row>
-              <entry>Repository documentation:</entry>
-              <entry><ulink url="https://repmgr.org/docs/current/installation-packages.html#INSTALLATION-PACKAGES-REDHAT-2NDQ">https://repmgr.org/docs/current/installation-packages.html#INSTALLATION-PACKAGES-REDHAT-2NDQ</ulink></entry>
-            </row>
-          </tbody>
-        </tgroup>
-      </table>
-
-      <table id="centos-pgdg-repository">
-        <title>PostgreSQL community repository (PGDG)</title>
-        <tgroup cols="2">
-          <tbody>
-            <row>
-              <entry>Repository URL:</entry>
-              <entry><ulink url="https://yum.postgresql.org/repopackages.php">https://yum.postgresql.org/repopackages.php</ulink></entry>
-            </row>
-            <row>
-              <entry>Repository documentation:</entry>
-              <entry><ulink url="https://yum.postgresql.org/">https://yum.postgresql.org/</ulink></entry>
-            </row>
-          </tbody>
-        </tgroup>
-      </table>
-
-    </sect2>
-
-    <sect2 id="packages-centos-details">
-      <title>CentOS package details</title>
-
-      <para>
-        The two tables below list relevant information, paths, commands etc. for the &repmgr; packages on
-        CentOS 7 (with systemd) and CentOS 6 (no systemd). Substitute the appropriate PostgreSQL major
-        version number for your installation.
-      </para>
-
-      <note>
-        <para>
-          For PostgreSQL 9.6 and lower, the CentOS packages use a mixture of <literal>9.6</literal>
-          and <literal>96</literal> in various places to designate the major version; e.g. the
-          package name is <literal>repmgr96</literal>, but the binary directory is
-          <filename>/var/lib/pgsql/9.6/data</filename>.
-        </para>
-        <para>
-          From PostgreSQL 10, the first part of the version number (e.g. <literal>10</literal>) is
-          the major version, so there is more consistency in file/path/package naming
-          (package <literal>repmgr10</literal>, binary directory <filename>/var/lib/pgsql/10/data</filename>).
-        </para>
-      </note>
-
-
-  <table id="centos-7-packages">
-   <title>CentOS 7 packages</title>
-
-   <tgroup cols="2">
-    <tbody>
-
-     <row>
-      <entry>Package name example:</entry>
-      <entry><filename>repmgr11-4.4.0-1.rhel7.x86_64</filename></entry>
-     </row>
-
-     <row>
-      <entry>Metapackage:</entry>
-      <entry>(none)</entry>
-     </row>
-
-     <row>
-      <entry>Installation command:</entry>
-      <entry><literal>yum install repmgr11</literal></entry>
-     </row>
-
-     <row>
-      <entry>Binary location:</entry>
-      <entry><filename>/usr/pgsql-11/bin</filename></entry>
-     </row>
-
-     <row>
-      <entry>repmgr in default path:</entry>
-      <entry>NO</entry>
-     </row>
-
-     <row>
-      <entry>Configuration file location:</entry>
-      <entry><filename>/etc/repmgr/11/repmgr.conf</filename></entry>
-     </row>
-
-     <row>
-      <entry>Data directory:</entry>
-      <entry><filename>/var/lib/pgsql/11/data</filename></entry>
-     </row>
-
-     <row>
-      <entry>repmgrd service command:</entry>
-      <entry><command>systemctl [start|stop|restart|reload] repmgr11</command></entry>
-     </row>
-
-     <row>
-      <entry>repmgrd service file location:</entry>
-      <entry><filename>/usr/lib/systemd/system/repmgr11.service</filename></entry>
-     </row>
-
-     <row>
-      <entry>repmgrd log file location:</entry>
-      <entry>(not specified by package; set in <filename>repmgr.conf</filename>)</entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <table id="centos-6-packages">
-   <title>CentOS 6 packages</title>
-
-   <tgroup cols="2">
-    <tbody>
-
-     <row>
-      <entry>Package name example:</entry>
-      <entry><filename>repmgr96-4.0.4-1.rhel6.x86_64</filename></entry>
-     </row>
-
-     <row>
-      <entry>Metapackage:</entry>
-      <entry>(none)</entry>
-     </row>
-
-     <row>
-      <entry>Installation command:</entry>
-      <entry><literal>yum install repmgr96</literal></entry>
-     </row>
-
-     <row>
-      <entry>Binary location:</entry>
-      <entry><filename>/usr/pgsql-9.6/bin</filename></entry>
-     </row>
-
-     <row>
-      <entry>repmgr in default path:</entry>
-      <entry>NO</entry>
-     </row>
-
-     <row>
-      <entry>Configuration file location:</entry>
-      <entry><filename>/etc/repmgr/9.6/repmgr.conf</filename></entry>
-     </row>
-
-     <row>
-      <entry>Data directory:</entry>
-      <entry><filename>/var/lib/pgsql/9.6/data</filename></entry>
-     </row>
-
-     <row>
-      <entry>repmgrd service command:</entry>
-      <entry><literal>service [start|stop|restart|reload] repmgr-9.6</literal></entry>
-     </row>
-
-     <row>
-      <entry>repmgrd service file location:</entry>
-      <entry><literal>/etc/init.d/repmgr-9.6</literal></entry>
-     </row>
-
-     <row>
-      <entry>repmgrd log file location:</entry>
-      <entry><filename>/var/log/repmgr/repmgrd-9.6.log</filename></entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-    </sect2>
- </sect1>
-
-
-
-
-  <sect1 id="packages-debian-ubuntu" xreflabel="Debian/Ubuntu packages">
-    <title>Debian/Ubuntu Packages</title>
-    <indexterm>
-      <primary>packages</primary>
-      <secondary>Debian/Ubuntu packages</secondary>
-    </indexterm>
-
-    <indexterm>
-      <primary>Debian/Ubuntu</primary>
-      <secondary>package information</secondary>
-    </indexterm>
-
-    <para>
-      &repmgr; <literal>.deb</literal> packages are provided by EDB as well as the
-      PostgreSQL Community APT repository, and are available for each community-supported
-      PostgreSQL version, currently supported Debian releases, and currently supported
-      Ubuntu LTS releases.
-    </para>
-
-    <sect2 id="packages-apt-repository">
-      <title>APT repositories</title>
-
-      <table id="apt-2ndquadrant-repository">
-        <title>EDB public repository</title>
-        <tgroup cols="2">
-          <tbody>
-            <row>
-              <entry>Repository URL:</entry>
-              <entry><ulink url="https://dl.enterprisedb.com/">https://dl.enterprisedb.com/</ulink></entry>
-            </row>
-            <row>
-              <entry>Repository documentation:</entry>
-              <entry><ulink url="https://repmgr.org/docs/current/installation-packages.html#INSTALLATION-PACKAGES-DEBIAN">https://repmgr.org/docs/current/installation-packages.html#INSTALLATION-PACKAGES-DEBIAN</ulink></entry>
-            </row>
-          </tbody>
-        </tgroup>
-      </table>
-
-
-      <table id="apt-repository">
-        <title>PostgreSQL Community APT repository (PGDG)</title>
-        <tgroup cols="2">
-          <tbody>
-            <row>
-              <entry>Repository URL:</entry>
-              <entry><ulink url="https://apt.postgresql.org/">https://apt.postgresql.org/</ulink></entry>
-            </row>
-            <row>
-              <entry>Repository documentation:</entry>
-              <entry><ulink url="https://wiki.postgresql.org/wiki/Apt">https://wiki.postgresql.org/wiki/Apt</ulink></entry>
-            </row>
-          </tbody>
-        </tgroup>
-      </table>
-    </sect2>
-
-   <sect2 id="packages-debian-details">
-      <title>Debian/Ubuntu package details</title>
-
-      <para>
-        The table below lists relevant information, paths, commands etc. for the &repmgr; packages on
-        Debian 9.x ("Stretch"). Substitute the appropriate PostgreSQL major
-        version number for your installation.
-      </para>
-      <para>
-        See also <xref linkend="repmgrd-configuration-debian-ubuntu"/> for some specifics related
-        to configuring the &repmgrd; daemon.
-      </para>
-
-      <table id="debian-9-packages">
-        <title>Debian 9.x packages</title>
-
-        <tgroup cols="2">
-          <tbody>
-
-            <row>
-              <entry>Package name example:</entry>
-              <entry><filename>postgresql-11-repmgr</filename></entry>
-            </row>
-
-            <row>
-              <entry>Metapackage:</entry>
-              <entry><filename>repmgr-common</filename></entry>
-            </row>
-
-            <row>
-              <entry>Installation command:</entry>
-              <entry><literal>apt-get install postgresql-11-repmgr</literal></entry>
-            </row>
-
-            <row>
-              <entry>Binary location:</entry>
-              <entry><filename>/usr/lib/postgresql/11/bin</filename></entry>
-            </row>
-
-            <row>
-              <entry>repmgr in default path:</entry>
-              <entry>Yes (via wrapper script <filename>/usr/bin/repmgr</filename>)</entry>
-            </row>
-
-            <row>
-              <entry>Configuration file location:</entry>
-              <entry>(not set by package)</entry>
-            </row>
-
-            <row>
-              <entry>Data directory:</entry>
-              <entry><filename>/var/lib/postgresql/11/main</filename></entry>
-            </row>
-
-            <row>
-              <entry>PostgreSQL service command:</entry>
-              <entry><command>systemctl [start|stop|restart|reload] postgresql@11-main</command></entry>
-
-            </row>
-
-            <row>
-              <entry>repmgrd service command:</entry>
-              <entry><command>systemctl [start|stop|restart|reload] repmgrd</command></entry>
-            </row>
-
-            <row>
-              <entry>repmgrd service file location:</entry>
-              <entry><filename>/etc/init.d/repmgrd</filename> (defaults in: <filename>/etc/defaults/repmgrd</filename>)</entry>
-            </row>
-
-            <row>
-              <entry>repmgrd log file location:</entry>
-              <entry>(not specified by package; set in <filename>repmgr.conf</filename>)</entry>
-            </row>
-
-          </tbody>
-        </tgroup>
-      </table>
-      <note>
-        <para>
-          When using Debian packages, instead of using the <application>systemd</application> service
-          command directly,  it's recommended to execute <command>pg_ctlcluster</command>
-          (as <literal>root</literal>, either directly or via <command>sudo</command>), e.g.:
-          <programlisting>
-            <command>pg_ctlcluster 11 main [start|stop|restart|reload]</command></programlisting>
-        </para>
-        <para>
-          For pre-<application>systemd</application> systems, <command>pg_ctlcluster</command>
-          can be executed directly by the <literal>postgres</literal> user.
-        </para>
-      </note>
-   </sect2>
-
-  </sect1>
-
-  <sect1 id="packages-snapshot" xreflabel="Snapshot packages">
-    <title>Snapshot packages</title>
-    <indexterm>
-      <primary>snapshot packages</primary>
-    </indexterm>
-    <indexterm>
-      <primary>packages</primary>
-      <secondary>snapshots</secondary>
-    </indexterm>
-
-    <para>
-      For testing new features and bug fixes, from time to time EDB provides
-      so-called &quot;snapshot packages&quot; via its public repository. These packages
-      are built from the &repmgr; source at a particular point in time, and are not formal
-      releases.
-    </para>
-    <note>
-      <para>
-        We do not recommend installing these packages in a production environment
-        unless specifically advised.
-      </para>
-    </note>
-    <para>
-      To install a snapshot package, it's necessary to install the EDB public snapshot repository,
-      following the instructions here: <ulink url="https://dl.enterprisedb.com/default/release/site/">https://dl.enterprisedb.com/default/release/site/</ulink> but replace <literal>release</literal> with <literal>snapshot</literal>
-      in the appropriate URL.
-    </para>
-    <para>
-      For example, to install the snapshot RPM repository for PostgreSQL 9.6, execute (as <literal>root</literal>):
-      <programlisting>
-curl https://dl.enterprisedb.com/default/snapshot/get/9.6/rpm | bash</programlisting>
-
-      or as a normal user with root sudo access:
-      <programlisting>
-curl https://dl.enterprisedb.com/default/snapshot/get/9.6/rpm | sudo bash</programlisting>
-    </para>
-    <para>
-      Alternatively you can browse the repository here:
-      <ulink url="https://dl.enterprisedb.com/default/snapshot/browse/">https://dl.enterprisedb.com/default/snapshot/browse/</ulink>.
-    </para>
-    <para>
-      Once the repository is installed, installing or updating &repmgr; will result in the latest snapshot
-      package being installed.
-    </para>
-    <para>
-      The package name will be formatted like this:
-      <programlisting>
-repmgr96-4.1.1-0.0git320.g5113ab0.1.el7.x86_64.rpm</programlisting>
-      containing the snapshot build number (here: <literal>320</literal>) and the hash
-      of the <application>git</application> commit it was built from (here: <literal>g5113ab0</literal>).
-    </para>
-
-    <para>
-      Note that the next formal release (in the above example <literal>4.1.1</literal>), once available,
-      will install in place of any snapshot builds.
-    </para>
-
-  </sect1>
-
-  <sect1 id="packages-old-versions" xreflabel="Installing old package versions">
-    <title>Installing old package versions</title>
-
-    <indexterm>
-      <primary>old packages</primary>
-    </indexterm>
-
-    <indexterm>
-      <primary>packages</primary>
-      <secondary>old versions</secondary>
-    </indexterm>
-
-    <indexterm>
-      <primary>installation</primary>
-      <secondary>old package versions</secondary>
-    </indexterm>
-
-    <sect2 id="packages-old-versions-debian" xreflabel="old Debian package versions">
-      <title>Debian/Ubuntu</title>
-      <para>
-        An archive of old packages (<literal>3.3.2</literal> and later) for Debian/Ubuntu-based systems is available here:
-        <ulink url="https://apt-archive.postgresql.org/">https://apt-archive.postgresql.org/</ulink>
-      </para>
-    </sect2>
-
-    <sect2 id="packages-old-versions-rhel-centos" xreflabel="old RHEL/CentOS package versions">
-      <title>RHEL/CentOS</title>
-
-      <para>
-        Old versions can be located with e.g.:
-        <programlisting>
-          yum --showduplicates list repmgr96</programlisting>
-        (substitute the appropriate package name; see <xref linkend="packages-centos"/>) and installed with:
-        <programlisting>
-          yum install {package_name}-{version}</programlisting>
-        where <literal>{package_name}</literal> is the base package name (e.g. <literal>repmgr96</literal>)
-        and <literal>{version}</literal> is the version listed by the
-        <command> yum --showduplicates list ...</command> command, e.g. <literal>4.0.6-1.rhel6</literal>.
-      </para>
-      <para>For example:
-        <programlisting>
-          yum install repmgr96-4.0.6-1.rhel6</programlisting>
-      </para>
-
-    </sect2>
-  </sect1>
-
-
-  <sect1 id="packages-packager-info" xreflabel="Information for packagers">
-    <title>Information for packagers</title>
-    <indexterm>
-      <primary>packages</primary>
-      <secondary>information for packagers</secondary>
-    </indexterm>
-    <para>
-      We recommend patching the following parameters when
-      building the package as built-in default values for user convenience.
-      These values can nevertheless be overridden by the user, if desired.
-    </para>
-    <itemizedlist>
-      <listitem>
-        <para>
-          Configuration file location: the default configuration file location
-          can be hard-coded by patching <varname>package_conf_file</varname>
-          in <filename>configfile.c</filename>:
-          <programlisting>
-		/* packagers: if feasible, patch configuration file path into "package_conf_file" */
-		char		package_conf_file[MAXPGPATH] = "";</programlisting>
-        </para>
-        <para>
-          See also: <xref linkend="configuration-file"/>
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          PID file location: the default &repmgrd; PID file
-          location can be hard-coded by patching <varname>package_pid_file</varname>
-          in <filename>repmgrd.c</filename>:
-          <programlisting>
-		/* packagers: if feasible, patch PID file path into "package_pid_file" */
-		char		package_pid_file[MAXPGPATH] = "";</programlisting>
-        </para>
-        <para>
-          See also: <xref linkend="repmgrd-pid-file"/>
-        </para>
-      </listitem>
-
-    </itemizedlist>
-  </sect1>
-</appendix>

doc/appendix-signatures.xml

@@ -1,37 +0,0 @@
-<appendix id="appendix-signatures" xreflabel="Verifying digital signatures">
- <title>Verifying digital signatures</title>
-
- <sect1 id="repmgr-source-key" xreflabel="repmgr source key">
-   <title>repmgr source code signing key</title>
-   <para>
-     The signing key ID used for <application>repmgr</application> source code bundles is:
-     <ulink url="https://repmgr.org/download/SOURCE-GPG-KEY-repmgr">
-       <literal>0x297F1DCC</literal></ulink>.
-   </para>
-
-   <para>
-     To download the <application>repmgr</application> source key to your computer:
-     <programlisting>
-       curl -s https://repmgr.org/download/SOURCE-GPG-KEY-repmgr | gpg --import
-       gpg --fingerprint 0x297F1DCC
-     </programlisting>
-     then verify that the fingerprint is the expected value:
-     <programlisting>
-       085A BE38 6FD9 72CE 6365  340D 8365 683D 297F 1DCC</programlisting>
-   </para>
-
-   <para>
-     For checking tarballs, first download and import the <application>repmgr</application>
-     source signing key as shown above. Then download both source tarball and the detached
-     key (e.g. <filename>repmgr-4.0beta1.tar.gz</filename> and
-     <filename>repmgr-4.0beta1.tar.gz.asc</filename>) from
-     <ulink url="https://repmgr.org/download/">https://repmgr.org/download/</ulink>
-     and use <application>gpg</application> to verify the key, e.g.:
-     <programlisting>
-       gpg --verify repmgr-4.0beta1.tar.gz.asc</programlisting>
-   </para>
-
- </sect1>
-
-
-</appendix>

doc/appendix-support.xml

@@ -1,114 +0,0 @@
-<appendix id="appendix-support" xreflabel="repmgr support">
-
-  <title>&repmgr; support</title>
-
-  <indexterm>
-    <primary>support</primary>
-  </indexterm>
-
-  <para>
-    <ulink url="https://www.enterprisedb.com/">EDB</ulink> provides 24x7
-    production support for &repmgr; and other PostgreSQL
-    products, including configuration assistance, installation
-    verification and training for running a robust replication cluster.
-  </para>
-  <para>
-    For further details see: <ulink url="https://www.enterprisedb.com/support/postgresql-support-overview-get-the-most-out-of-postgresql">Support Center</ulink>
-  </para>
-
-  <para>
-    A mailing list/forum is provided via Google groups to discuss contributions or issues: <ulink url="https://groups.google.com/group/repmgr">https://groups.google.com/group/repmgr</ulink>.
-  </para>
-  <para>
-    Please report bugs and other issues to: <ulink url="https://github.com/EnterpriseDB/repmgr">https://github.com/EnterpriseDB/repmgr</ulink>.
-  </para>
-
-  <important>
-    <para>
-      Please read the <link linkend="appendix-support-reporting-issues">following section</link> before submitting questions or issue reports.
-    </para>
-  </important>
-
-  <sect1 id="appendix-support-reporting-issues" xreflabel="Reportins Issues">
-    <title>Reporting Issues</title>
-
-    <indexterm>
-      <primary>support</primary>
-      <secondary>reporting issues</secondary>
-    </indexterm>
-
-
-    <para>
-      When asking questions or reporting issues, it is extremely helpful if the following information is included:
-
-    <itemizedlist spacing="compact" mark="bullet">
-
-     <listitem>
-      <simpara>
-        PostgreSQL version
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        &repmgr; version
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        How was &repmgr; installed? From source? From packages? If
-        so from which repository?
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        <filename>repmgr.conf</filename> files (suitably anonymized if necessary)
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        Contents of the <literal>repmgr.nodes</literal> table (suitably anonymized if necessary)
-      </simpara>
-     </listitem>
-
-
-     <listitem>
-      <simpara>
-        PostgreSQL 11 and earlier: contents of the <filename>recovery.conf</filename> file
-        (suitably anonymized if necessary).
-      </simpara>
-     </listitem>
-     <listitem>
-      <simpara>
-        PostgreSQL 12 and later: contents of the <filename>postgresql.auto.conf</filename> file
-        (suitably anonymized if necessary), and whether or not the PostgreSQL data directory
-        contains the files <filename>standby.signal</filename> and/or <filename>recovery.signal</filename>.
-      </simpara>
-     </listitem>
-
-    </itemizedlist>
-    </para>
-    <para>
-      If issues are encountered with a &repmgr; client command, please provide
-      the output of that command executed with the options
-      <option>-LDEBUG --verbose</option>, which will ensure &repmgr; emits
-      the maximum level of logging output.
-    </para>
-    <para>
-      If issues are encountered with &repmgrd;,
-      please provide relevant extracts from the &repmgr; log files
-      and if possible the PostgreSQL log itself. Please ensure these
-      logs do not contain any confidential data.
-    </para>
-    <para>
-      In all cases it is <emphasis>extremely</emphasis> useful to receive
-      as much detail as possible on how to reliably reproduce
-      an issue.
-    </para>
-
-  </sect1>
-
-</appendix>

doc/bdr-failover.md

@@ -0,0 +1,288 @@
+BDR failover with repmgrd
+=========================
+
+`repmgr 4` provides support for monitoring BDR nodes and taking action in case
+one of the nodes fails.
+
+    *NOTE* Due to the nature of BDR, it's only safe to use this solution for
+    a two-node scenario. Introducing additional nodes will create an inherent
+    risk of node desynchronisation if a node goes down without being cleanly
+    removed from the cluster.
+
+In contrast to streaming replication, there's no concept of "promoting" a new
+primary node with BDR. Instead, "failover" involves monitoring both nodes
+with `repmgrd` and redirecting queries from the failed node to the remaining
+active node. This can be done by using the event notification script generated by
+`repmgrd` to dynamically reconfigure a proxy server/connection pooler such
+as PgBouncer.
+
+
+Prerequisites
+-------------
+
+`repmgr 4` requires PostgreSQL 9.6 with the BDR 2 extension enabled and
+configured for a two-node BDR network. `repmgr 4` packages
+must be installed on each node before attempting to configure repmgr.
+
+    *NOTE* `repmgr 4` will refuse to install if it detects more than two
+    BDR nodes.
+
+Application database connections *must* be passed through a proxy server/
+connection pooler such as PgBouncer, and it must be possible to dynamically
+reconfigure that from `repmgrd`. The example demonstrated in this document
+will use PgBouncer.
+
+The proxy server / connection poolers must not be installed on the database
+servers.
+
+For this example, it's assumed password-less SSH connections are available
+from the PostgreSQL servers to the servers where PgBouncer runs, and
+that the user on those servers has permission to alter the PgBouncer
+configuration files.
+
+PostgreSQL connections must be possible between each node, and each node
+must be able to connect to each PgBouncer instance.
+
+
+Configuration
+-------------
+
+Sample configuration for `repmgr.conf`:
+
+    node_id=1
+    node_name='node1'
+    conninfo='host=node1 dbname=bdrtest user=repmgr connect_timeout=2'
+    replication_type='bdr'
+
+    event_notifications=bdr_failover
+    event_notification_command='/path/to/bdr-pgbouncer.sh %n %e %s "%c" "%a" >> /tmp/bdr-failover.log 2>&1'
+
+    # repmgrd options
+    monitor_interval_secs=5
+    reconnect_attempts=6
+    reconnect_interval=5
+
+Adjust settings as appropriate; copy and adjust for the second node (particularly
+the values `node_id`, `node_name` and `conninfo`).
+
+Note that the values provided for the `conninfo` string must be valid for
+connections from *both* nodes in the cluster. The database must be the BDR
+database.
+
+If defined, `event_notifications` will restrict execution of `event_notification_command`
+to the specified events.
+
+`event_notification_command` is the script which does the actual "heavy lifting"
+of reconfiguring the proxy server/ connection pooler. It is fully user-definable;
+a sample implementation is documented below.
+
+
+repmgr user permissions
+-----------------------
+
+`repmgr` will create an extension in the BDR database containing objects
+for administering `repmgr` metadata. The user defined in the `conninfo`
+setting must be able to access all objects. Additionally, superuser permissions
+are required to install the `repmgr` extension. The easiest way to do this
+is create the `repmgr` user as a superuser, however if this is not
+desirable, the `repmgr` user can be created as a normal user and a
+superuser specified with `--superuser` when registering a BDR node.
+
+repmgr setup
+------------
+
+Register both nodes:
+
+    $ repmgr -f /etc/repmgr.conf bdr register
+    NOTICE: attempting to install extension "repmgr"
+    NOTICE: "repmgr" extension successfully installed
+    NOTICE: node record created for node 'node1' (ID: 1)
+    NOTICE: BDR node 1 registered (conninfo: host=localhost dbname=bdrtest user=repmgr port=5501)
+
+    $ repmgr -f /etc/repmgr.conf bdr register
+    NOTICE: node record created for node 'node2' (ID: 2)
+    NOTICE: BDR node 2 registered (conninfo: host=localhost dbname=bdrtest user=repmgr port=5502)
+
+The `repmgr` extension will be automatically created when the first
+node is registered, and will be propagated to the second node.
+
+    *IMPORTANT* ensure the repmgr package is available on both nodes before
+    attempting to register the first node
+
+
+At this point the meta data for both nodes has been created; executing
+`repmgr cluster show` (on either node) should produce output like this:
+
+    $ repmgr -f /etc/repmgr.conf cluster show
+     ID | Name  | Role | Status    | Upstream | Connection string
+    ----+-------+------+-----------+----------+--------------------------------------------------------
+     1  | node1 | bdr  | * running |          | host=node1 dbname=bdrtest user=repmgr connect_timeout=2
+     2  | node2 | bdr  | * running |          | host=node2 dbname=bdrtest user=repmgr connect_timeout=2
+
+Additionally it's possible to see a log of significant events; so far
+this will only record the two node registrations (in reverse chronological order):
+
+     Node ID | Event        | OK | Timestamp           | Details
+    ---------+--------------+----+---------------------+----------------------------------------------
+     2       | bdr_register | t  | 2017-07-27 17:51:48 | node record created for node 'node2' (ID: 2)
+     1       | bdr_register | t  | 2017-07-27 17:51:00 | node record created for node 'node1' (ID: 1)
+
+
+Defining the "event_notification_command"
+-----------------------------------------
+
+Key to "failover" execution is the `event_notification_command`, which is a
+user-definable script which should reconfigure the  proxy server/
+connection pooler.
+
+Each time `repmgr` (or `repmgrd`) records an event, it can optionally
+execute the script defined in `event_notification_command` to
+take further action; details of the event will be passed as parameters.
+Following placeholders are available to the script:
+
+    %n - node ID
+    %e - event type
+    %s - success (1 or 0)
+    %t - timestamp
+    %d - details
+    %c - conninfo string of the next available node
+    %a - name of the next available node
+
+Note that `%c` and `%a` will only be provided during `bdr_failover`
+events, which is what is of interest here.
+
+The provided sample script (`scripts/bdr-pgbouncer.sh`) is configured like
+this:
+
+    event_notification_command='/path/to/bdr-pgbouncer.sh %n %e %s "%c" "%a"'
+
+and parses the configures parameters like this:
+
+    NODE_ID=$1
+    EVENT_TYPE=$2
+    SUCCESS=$3
+    NEXT_CONNINFO=$4
+    NEXT_NODE_NAME=$5
+
+It also contains some hard-coded values about the PgBouncer configuration for
+both nodes; these will need to be adjusted for your local environment of course
+(ideally the scripts would be maintained as templates and generated by some
+kind of provisioning system).
+
+The script performs following steps:
+
+ - pauses PgBouncer on all nodes
+ - recreates the PgBouncer configuration file on each node using the information
+   provided by `repmgrd` (mainly the `conninfo` string) to configure PgBouncer
+   to point to the remaining node
+ - reloads the PgBouncer configuration
+ - resumes PgBouncer
+
+From that point, any connections to PgBouncer on the failed BDR node will be redirected
+to the active node.
+
+
+repmgrd
+-------
+
+
+
+Node monitoring and failover
+----------------------------
+
+At the intervals specified by `monitor_interval_secs` in `repmgr.conf`, `repmgrd`
+will ping each node to check if it's available. If a node isn't available,
+`repmgrd` will enter failover mode and  check `reconnect_attempts` times
+at intervals of `reconnect_interval` to confirm the node is definitely unreachable.
+This buffer period is necessary to avoid false positives caused by transient
+network outages.
+
+If the node is still unavailable, `repmgrd` will enter failover mode and execute
+the script defined in `event_notification_command`; an entry will be logged
+in the `repmgr.events` table and `repmgrd` will (unless otherwise configured)
+resume monitoring of the node in "degraded" mode until it reappears.
+
+`repmgrd` logfile output during a failover event will look something like this
+one one node (usually the node which has failed, here "node2"):
+
+    ...
+    [2017-07-27 21:08:39] [INFO] starting continuous BDR node monitoring
+    [2017-07-27 21:08:39] [INFO] monitoring BDR replication status on node "node2" (ID: 2)
+    [2017-07-27 21:08:55] [INFO] monitoring BDR replication status on node "node2" (ID: 2)
+    [2017-07-27 21:09:11] [INFO] monitoring BDR replication status on node "node2" (ID: 2)
+    [2017-07-27 21:09:23] [WARNING] unable to connect to node node2 (ID 2)
+    [2017-07-27 21:09:23] [INFO] checking state of node 2, 0 of 5 attempts
+    [2017-07-27 21:09:23] [INFO] sleeping 1 seconds until next reconnection attempt
+    [2017-07-27 21:09:24] [INFO] checking state of node 2, 1 of 5 attempts
+    [2017-07-27 21:09:24] [INFO] sleeping 1 seconds until next reconnection attempt
+    [2017-07-27 21:09:25] [INFO] checking state of node 2, 2 of 5 attempts
+    [2017-07-27 21:09:25] [INFO] sleeping 1 seconds until next reconnection attempt
+    [2017-07-27 21:09:26] [INFO] checking state of node 2, 3 of 5 attempts
+    [2017-07-27 21:09:26] [INFO] sleeping 1 seconds until next reconnection attempt
+    [2017-07-27 21:09:27] [INFO] checking state of node 2, 4 of 5 attempts
+    [2017-07-27 21:09:27] [INFO] sleeping 1 seconds until next reconnection attempt
+    [2017-07-27 21:09:28] [WARNING] unable to reconnect to node 2 after 5 attempts
+    [2017-07-27 21:09:28] [NOTICE] setting node record for node 2 to inactive
+    [2017-07-27 21:09:28] [INFO] executing notification command for event "bdr_failover"
+    [2017-07-27 21:09:28] [DETAIL] command is:
+      /path/to/bdr-pgbouncer.sh 2 bdr_failover 1 "host=host=node1 dbname=bdrtest user=repmgr connect_timeout=2" "node1"
+    [2017-07-27 21:09:28] [INFO] node 'node2' (ID: 2) detected as failed; next available node is 'node1' (ID: 1)
+    [2017-07-27 21:09:28] [INFO] monitoring BDR replication status on node "node2" (ID: 2)
+    [2017-07-27 21:09:28] [DETAIL] monitoring node "node2" (ID: 2) in degraded mode
+    ...
+
+Output on the other node ("node1") during the same event will look like this:
+
+    [2017-07-27 21:08:35] [INFO] starting continuous BDR node monitoring
+    [2017-07-27 21:08:35] [INFO] monitoring BDR replication status on node "node1" (ID: 1)
+    [2017-07-27 21:08:51] [INFO] monitoring BDR replication status on node "node1" (ID: 1)
+    [2017-07-27 21:09:07] [INFO] monitoring BDR replication status on node "node1" (ID: 1)
+    [2017-07-27 21:09:23] [WARNING] unable to connect to node node2 (ID 2)
+    [2017-07-27 21:09:23] [INFO] checking state of node 2, 0 of 5 attempts
+    [2017-07-27 21:09:23] [INFO] sleeping 1 seconds until next reconnection attempt
+    [2017-07-27 21:09:24] [INFO] checking state of node 2, 1 of 5 attempts
+    [2017-07-27 21:09:24] [INFO] sleeping 1 seconds until next reconnection attempt
+    [2017-07-27 21:09:25] [INFO] checking state of node 2, 2 of 5 attempts
+    [2017-07-27 21:09:25] [INFO] sleeping 1 seconds until next reconnection attempt
+    [2017-07-27 21:09:26] [INFO] checking state of node 2, 3 of 5 attempts
+    [2017-07-27 21:09:26] [INFO] sleeping 1 seconds until next reconnection attempt
+    [2017-07-27 21:09:27] [INFO] checking state of node 2, 4 of 5 attempts
+    [2017-07-27 21:09:27] [INFO] sleeping 1 seconds until next reconnection attempt
+    [2017-07-27 21:09:28] [WARNING] unable to reconnect to node 2 after 5 attempts
+    [2017-07-27 21:09:28] [NOTICE] other node's repmgrd is handling failover
+    [2017-07-27 21:09:28] [INFO] monitoring BDR replication status on node "node1" (ID: 1)
+    [2017-07-27 21:09:28] [DETAIL] monitoring node "node2" (ID: 2) in degraded mode
+
+This assumes only the PostgreSQL instance on "node2" has failed. In this case the
+`repmgrd` instance running on "node2" has performed the failover. However if
+the entire server becomes unavailable, `repmgrd` on "node1" will perform
+the failover.
+
+
+Node recovery
+-------------
+
+Following failure of a BDR node, if the node subsequently becomes available again,
+a `bdr_recovery` event will be generated. This could potentially be used to
+reconfigure PgBouncer automatically to bring the node back into the available pool,
+however it would be prudent to manually verify the node's status before
+exposing it to the application.
+
+If the failed node comes back up and connects correctly, output similar to this
+will be visible in the `repmgrd` log:
+
+    [2017-07-27 21:25:30] [DETAIL] monitoring node "node2" (ID: 2) in degraded mode
+    [2017-07-27 21:25:46] [INFO] monitoring BDR replication status on node "node2" (ID: 2)
+    [2017-07-27 21:25:46] [DETAIL] monitoring node "node2" (ID: 2) in degraded mode
+    [2017-07-27 21:25:55] [INFO] active replication slot for node "node1" found after 1 seconds
+    [2017-07-27 21:25:55] [NOTICE] node "node2" (ID: 2) has recovered after 986 seconds
+
+
+Shutdown of both nodes
+----------------------
+
+If both PostgreSQL instances are shut down, `repmgrd` will try and handle the
+situation as gracefully as possible, though with no failover candidates available
+there's not much it can do. Should this case ever occur, we recommend shutting
+down `repmgrd` on both nodes and restarting it once the PostgreSQL instances
+are running properly.

doc/changes-in-repmgr4.md

@@ -1,7 +1,106 @@
-Changes in repmgr 4
-===================
 
-This document has been integrated into the main `repmgr` documentation
+Standardisation on `primary`
-and is now located here:
+----------------------------
 
-> [Release notes](https://repmgr.org/docs/current/release-4.0.html)
+To standardise terminology, `primary` is used to denote the read/write
+node in a streaming replication cluster. `master` is still accepted
+as a synonym (e.g. `repmgr master register`).
+
+
+New command line options
+------------------------
+
+- `--dry-run`: repmgr will attempt to perform the action as far as possible
+   without making any changes to the database
+
+- `--upstream-node-id`: use to specify the upstream node the standby will
+  connect later stream from, when cloning a standby. This replaces the configuration
+  file parameter `upstream_node`, as the upstream node is set when the standby
+  is initially cloned, but can change over the lifetime of an installation (due
+  to failovers, switchovers etc.) so it's pointless/confusing keeping the original
+  value around in the config file.
+
+Changed command line options
+----------------------------
+
+### repmgr
+
+- `--replication-user` has been deprecated; it has been replaced by the
+  configuration file option `replication_user`.  The value (which defaults
+  to the user in the `conninfo` string) will be stored in the repmgr metadata
+  for use by  standby clone/follow..
+
+- `--recovery-min-apply-delay` is now a configuration file parameter
+  `recovery_min_apply_delay, to ensure the setting does not get lost when
+  a standby follows a new upstream.
+
+### repmgrd
+
+- `--monitoring-history` is deprecated and has been replaced by the
+  configuration file option `monitoring_history`. This enables the
+  setting to be changed without having to modify system service files.
+
+Changes to repmgr commands
+--------------------------
+
+
+### `repmgr cluster show`
+
+This now displays the role of each node (e.g. `primary`, `standby`)
+and its status in separate columns.
+
+The `--csv` option now emits a third column indicating the recovery
+status of the node.
+
+
+Configuration file changes
+--------------------------
+
+### Required settings
+
+The following 4 parameters are mandatory in `repmgr.conf`:
+
+- `node_id`
+- `node_name`
+- `conninfo`
+- `data_directory`
+
+
+### Renamed settings
+
+Some settings have been renamed for clarity and consistency:
+
+- `node`: now `node_id`
+- `name`: now `node_name`
+- `master_reponse_timeout`: now `async_query_timeout` to better indicate its
+   purpose
+
+- The following configuration file parameters have been renamed for consistency
+  with other parameters (and conform to the pattern used by PostgreSQL itself,
+  which uses the prefix `log_` for logging parameters):
+  - `loglevel` has been renamed to `log_level`
+  - `logfile` has been renamed to `log_file`
+  - `logfacility` has been renamed to `log_facility`
+
+### Removed settings
+
+- `cluster`: has been removed
+- `upstream_node`: see note about `--upstream-node-id` above.
+- `retry_promote_interval_secs`: this is now redundant due to changes in the
+   failover/promotion mechanism; the new equivalent is `primary_notification_timeout`
+
+
+### Logging changes
+
+- default value for `log_level` is `INFO` rather than `NOTICE`.
+- new parameter `log_status_interval`, which causes `repmgrd` to emit a status log
+  line at the specified interval
+
+
+repmgrd
+-------
+
+The `repmgr` shared library has been renamed from `repmgr_funcs` to `repmgr`,
+meaning `shared_preload_libraries` needs to be updated to the new name:
+
+    shared_preload_libraries = 'repmgr'

doc/cloning-standbys.xml

@@ -1,651 +0,0 @@
-<chapter id="cloning-standbys" xreflabel="cloning standbys">
- <title>Cloning standbys</title>
-
- <sect1 id="cloning-from-barman" xreflabel="Cloning from Barman">
-   <title>Cloning a standby from Barman</title>
-
-   <indexterm>
-    <primary>cloning</primary>
-    <secondary>from Barman</secondary>
-   </indexterm>
-   <indexterm>
-    <primary>Barman</primary>
-    <secondary>cloning a standby</secondary>
-   </indexterm>
-
-   <para>
-    <xref linkend="repmgr-standby-clone"/> can use
-    <ulink url="https://www.enterprisedb.com/">EDB</ulink>'s
-    <ulink url="https://www.pgbarman.org/">Barman</ulink> application
-    to clone a standby (and also as a fallback source for WAL files).
-   </para>
-   <tip>
-    <simpara>
-     Barman (aka PgBarman) should be considered as an integral part of any
-     PostgreSQL replication cluster. For more details see:
-     <ulink url="https://www.pgbarman.org/">https://www.pgbarman.org/</ulink>.
-    </simpara>
-   </tip>
-   <para>
-    Barman support provides the following advantages:
-    <itemizedlist spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       the primary node does not need to perform a new backup every time a
-       new standby is cloned
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       a standby node can be disconnected for longer periods without losing
-       the ability to catch up, and without causing accumulation of WAL
-       files on the primary node
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       WAL management on the primary becomes much easier as there's no need
-       to use replication slots, and <varname>wal_keep_segments</varname>
-       (PostgreSQL 13 and later: <varname>wal_keep_size</varname>)
-       does not need to be set.
-     </para>
-    </listitem>
-   </itemizedlist>
-   </para>
-
-
-   <note>
-    <para>
-      Currently &repmgr;'s support for cloning from Barman is implemented by using
-      <productname>rsync</productname> to clone from the Barman server.
-    </para>
-    <para>
-      It is therefore not able to make use of Barman's parallel restore facility, which
-      is executed on the Barman server and clones to the target server.
-    </para>
-    <para>
-      Barman's parallel restore facility can be used by executing it manually on
-      the Barman server and configuring replication on the resulting cloned
-      standby using
-      <command><link linkend="repmgr-standby-clone">repmgr standby clone --replication-conf-only</link></command>.
-    </para>
-   </note>
-
-
-  <sect2 id="cloning-from-barman-prerequisites">
-   <title>Prerequisites for cloning from Barman</title>
-   <para>
-    In order to enable Barman support for <command>repmgr standby clone</command>, following
-    prerequisites must be met:
-   <itemizedlist spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-        the Barman catalogue must include at least one valid backup for this server;
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-        the <varname>barman_host</varname> setting in <filename>repmgr.conf</filename> is set to the SSH
-        hostname of the Barman server;
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-        the <varname>barman_server</varname> setting in <filename>repmgr.conf</filename> is the same as the
-        server configured in Barman.
-      </para>
-     </listitem>
-
-   </itemizedlist>
-   </para>
-
-   <para>
-     For example, assuming Barman is located on the host &quot;<literal>barmansrv</literal>&quot;
-     under the &quot;<literal>barman</literal>&quot; user account,
-     <filename>repmgr.conf</filename> should contain the following entries:
-    <programlisting>
-    barman_host='barman@barmansrv'
-    barman_server='pg'</programlisting>
-   </para>
-   <para>
-     Here <literal>pg</literal> corresponds to a section in Barman's configuration file for a specific
-     server backup configuration, which would look something like:
-     <programlisting>
-[pg]
-description = "Main cluster"
-...
-     </programlisting>
-   </para>
-   <para>
-     More details on Barman configuration can be found in the
-     <ulink url="https://docs.pgbarman.org/">Barman documentation</ulink>'s
-     <ulink url="https://docs.pgbarman.org/#configuration">configuration section</ulink>.
-   </para>
-   <note>
-    <para>
-     To use a non-default Barman configuration file on the Barman server,
-     specify this in <filename>repmgr.conf</filename> with <filename>barman_config</filename>:
-     <programlisting>
-      barman_config='/path/to/barman.conf'</programlisting>
-    </para>
-   </note>
-
-
-   <para>
-     We also recommend configuring the <varname>restore_command</varname> setting in <filename>repmgr.conf</filename>
-     to use the <command>barman-wal-restore</command> script
-     (see section <xref linkend="cloning-from-barman-restore-command"/> below).
-   </para>
-
-
-   <tip>
-    <simpara>
-      If you have a non-default SSH configuration on the Barman
-      server, e.g. using a port other than 22, then you can set those
-      parameters in a dedicated Host section in <filename>~/.ssh/config</filename>
-      corresponding to the value of <varname>barman_host</varname> in
-      <filename>repmgr.conf</filename>. See the <literal>Host</literal>
-      section in <command>man 5 ssh_config</command> for more details.
-    </simpara>
-   </tip>
-   <para>
-     If you wish to place WAL files in a location outside the main
-     PostgreSQL data directory, set <option>--waldir</option>
-     (PostgreSQL 9.6 and earlier: <option>--xlogdir</option>) in
-     <option>pg_basebackup_options</option> to the target directory
-     (must be an absolute filepath). &repmgr; will create and
-     symlink to this directory in exactly the same way
-     <application>pg_basebackup</application> would.
-   </para>
-   <para>
-    It's now possible to clone a standby from Barman, e.g.:
-    <programlisting>
-    $ repmgr -f /etc/repmgr.conf -h node1 -U repmgr -d repmgr standby clone
-    NOTICE: destination directory "/var/lib/postgresql/data" provided
-    INFO: connecting to Barman server to verify backup for "test_cluster"
-    INFO: checking and correcting permissions on existing directory "/var/lib/postgresql/data"
-    INFO: creating directory "/var/lib/postgresql/data/repmgr"...
-    INFO: connecting to Barman server to fetch server parameters
-    INFO: connecting to source node
-    DETAIL: current installation size is 30 MB
-    NOTICE: retrieving backup from Barman...
-    (...)
-    NOTICE: standby clone (from Barman) complete
-    NOTICE: you can now start your PostgreSQL server
-    HINT: for example: pg_ctl -D /var/lib/postgresql/data start</programlisting>
-   </para>
-
-   <note>
-    <simpara>
-     Barman support is automatically enabled if <varname>barman_server</varname>
-     is set. Normally it is good practice to use Barman, for instance
-     when fetching a base backup while cloning a standby; in any case,
-     Barman mode can be disabled using the <literal>--without-barman</literal>
-     command line option.
-    </simpara>
-   </note>
-
-  </sect2>
-  <sect2 id="cloning-from-barman-restore-command" xreflabel="Using Barman as a WAL file source">
-   <title>Using Barman as a WAL file source</title>
-
-   <indexterm>
-    <primary>Barman</primary>
-    <secondary>fetching archived WAL</secondary>
-   </indexterm>
-
-   <para>
-    As a fallback in case streaming replication is interrupted, PostgreSQL can optionally
-    retrieve WAL files from an archive, such as that provided by Barman. This is done by
-    setting <varname>restore_command</varname> in the replication configuration to
-    a valid shell command which can retrieve a specified WAL file from the archive.
-   </para>
-   <para>
-     <command>barman-wal-restore</command> is a Python script provided as part of the <literal>barman-cli</literal>
-     package (Barman 2.0 ~ 2.7) or as part of the core Barman distribution (Barman 2.8 and later).
-   </para>
-   <para>
-    To use <command>barman-wal-restore</command> with &repmgr;,
-    assuming Barman is located on the host &quot;<literal>barmansrv</literal>&quot;
-    under the &quot;<literal>barman</literal>&quot; user account,
-    and that <command>barman-wal-restore</command> is located as an executable at
-    <filename>/usr/bin/barman-wal-restore</filename>,
-    <filename>repmgr.conf</filename> should include the following lines:
-    <programlisting>
-    barman_host='barman@barmansrv'
-    barman_server='pg'
-    restore_command='/usr/bin/barman-wal-restore barmansrv pg %f %p'</programlisting>
-   </para>
-   <note>
-    <simpara>
-      <command>barman-wal-restore</command> supports command line switches to
-      control parallelism (<literal>--parallel=N</literal>) and compression
-      (<literal>--bzip2</literal>, <literal>--gzip</literal>).
-    </simpara>
-   </note>
-
-  </sect2>
-
-  <sect2 id="cloning-from-barman-pg_backupapi-mode" xreflabel="Using Barman through its API (pg-backup-api)">
-    <title>Using Barman through its API (pg-backup-api)</title>
-    <indexterm>
-      <primary>cloning</primary>
-      <secondary>pg-backup-api</secondary>
-    </indexterm>
-
-    <para>
-      You can find information on how to install and setup pg-backup-api in
-      <ulink url="https://www.enterprisedb.com/docs/supported-open-source/barman/pg-backup-api/">the pg-backup-api
-      documentation</ulink>.
-    </para>
-
-    <para>
-      This mode (`pg-backupapi`) was introduced in v5.4.0 as a way to further integrate with Barman letting Barman
-      handle the restore. This also reduces the ssh keys that need to share between the backup and postgres nodes.
-      As long as you have access to the API service by HTTP calls, you could perform recoveries right away.
-      You just need to instruct Barman through the API which backup you need and on which node the backup needs to
-      to be restored on.
-    </para>
-
-    <para>
-      In order to enable <literal>pg_backupapi mode</literal> support for <command>repmgr standby clone</command>,
-      you need the following lines in repmgr.conf:
-      <itemizedlist spacing="compact" mark="bullet">
-        <listitem><para>pg_backupapi_host: Where pg-backup-api is hosted</para></listitem>
-        <listitem><para>pg_backupapi_node_name: Name of the server as understood by Barman</para></listitem>
-        <listitem><para>pg_backupapi_remote_ssh_command: How Barman will be connecting as to the node</para></listitem>
-        <listitem><para>pg_backupapi_backup_id: ID of the existing backup you need to restore</para></listitem>
-      </itemizedlist>
-
-      This is an example of how repmgr.conf would look like:
-
-      <programlisting>
-        pg_backupapi_host = '192.168.122.154'
-        pg_backupapi_node_name = 'burrito'
-        pg_backupapi_remote_ssh_command = 'ssh john_doe@192.168.122.1'
-        pg_backupapi_backup_id = '20230223T093201'
-      </programlisting>
-    </para>
-
-    <para>
-      <literal>pg_backupapi_host</literal> is the variable name that enables this mode, and when you set it,
-      all the rest of the above variables are required. Also, remember that this service is just an interface
-      between Barman and repmgr, hence if something fails during a recovery, you should check Barman's logs upon
-      why the process couldn't finish properly.
-    </para>
-
-    <note>
-      <simpara>
-        Despite in Barman you can define shortcuts like "lastest" or "oldest", they are not supported for the
-        time being in pg-backup-api. These shortcuts will be supported in a future release.
-      </simpara>
-     </note>
-
-    <para>
-      This is a real example of repmgr's output cloning with the API. Note that during this operation, we stopped
-      the service for a little while and repmgr had to retry but that doesn't affect the final outcome. The primary
-      is listening on localhost's port 6001:
-
-      <programlisting>
-$ repmgr -f ~/nodes/node_3/repmgr.conf standby clone -U repmgr -p 6001 -h localhost
-NOTICE: destination directory "/home/mario/nodes/node_3/data" provided
-INFO: Attempting to use `pg_backupapi` new restore mode
-INFO: connecting to source node
-DETAIL: connection string is: user=repmgr port=6001 host=localhost
-DETAIL: current installation size is 8541 MB
-DEBUG: 1 node records returned by source node
-DEBUG: connecting to: "user=repmgr dbname=repmgr host=localhost port=6001 connect_timeout=2 fallback_application_name=repmgr options=-csearch_path="
-DEBUG: upstream_node_id determined as 1
-INFO: Attempting to use `pg_backupapi` new restore mode
-INFO: replication slot usage not requested;  no replication slot will be set up for this standby
-NOTICE: starting backup (using pg_backupapi)...
-INFO: Success creating the task: operation id '20230309T150647'
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-Incorrect reply received for that operation ID.
-INFO: Retrying...
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status IN_PROGRESS
-INFO: status DONE
-NOTICE: standby clone (from pg_backupapi) complete
-NOTICE: you can now start your PostgreSQL server
-HINT: for example: pg_ctl -D /home/mario/nodes/node_3/data start
-HINT: after starting the server, you need to register this standby with "repmgr standby register"
-      </programlisting>
-
-    </para>
-  </sect2> <!--END cloning-from-barman-pg_backupapi-mode !-->
- </sect1>
-
- <sect1 id="cloning-replication-slots" xreflabel="Cloning and replication slots">
-   <title>Cloning and replication slots</title>
-
-   <indexterm>
-     <primary>cloning</primary>
-     <secondary>replication slots</secondary>
-   </indexterm>
-
-   <indexterm>
-     <primary>replication slots</primary>
-     <secondary>cloning</secondary>
-   </indexterm>
-   <para>
-    Replication slots were introduced with PostgreSQL 9.4 and are designed to ensure
-    that any standby connected to the primary using a replication slot will always
-    be able to retrieve the required WAL files. This removes the need to manually
-    manage WAL file retention by estimating the number of WAL files that need to
-    be maintained on the primary using <varname>wal_keep_segments</varname>
-    (PostgreSQL 13 and later: <varname>wal_keep_size</varname>).
-    Do however be aware that if a standby is disconnected, WAL will continue to
-    accumulate on the primary until either the standby reconnects or the replication
-    slot is dropped.
-   </para>
-   <para>
-     To enable &repmgr; to use replication slots, set the boolean parameter
-     <varname>use_replication_slots</varname> in <filename>repmgr.conf</filename>:
-     <programlisting>
-       use_replication_slots=true</programlisting>
-   </para>
-   <para>
-    Replication slots must be enabled in <filename>postgresql.conf</filename> by
-    setting the parameter <varname>max_replication_slots</varname> to at least the
-    number of expected standbys (changes to this parameter require a server restart).
-   </para>
-   <para>
-    When cloning a standby, &repmgr; will automatically generate an appropriate
-    slot name, which is stored in the <literal>repmgr.nodes</literal> table, and create the slot
-    on the upstream node:
-     <programlisting>
-    repmgr=# SELECT node_id, upstream_node_id, active, node_name, type, priority, slot_name
-               FROM repmgr.nodes ORDER BY node_id;
-     node_id | upstream_node_id | active | node_name |  type   | priority |   slot_name
-    ---------+------------------+--------+-----------+---------+----------+---------------
-           1 |                  | t      | node1     | primary |      100 | repmgr_slot_1
-           2 |                1 | t      | node2     | standby |      100 | repmgr_slot_2
-           3 |                1 | t      | node3     | standby |      100 | repmgr_slot_3
-     (3 rows)</programlisting>
-
-    <programlisting>
-    repmgr=# SELECT slot_name, slot_type, active, active_pid FROM pg_replication_slots ;
-       slot_name   | slot_type | active | active_pid
-    ---------------+-----------+--------+------------
-     repmgr_slot_2 | physical  | t      |      23658
-     repmgr_slot_3 | physical  | t      |      23687
-    (2 rows)</programlisting>
-   </para>
-   <para>
-    Note that a slot name will be created by default for the primary but not
-    actually used unless the primary is converted to a standby using e.g.
-    <command>repmgr standby switchover</command>.
-   </para>
-   <para>
-    Further information on replication slots in the PostgreSQL documentation:
-    <ulink url="https://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</ulink>
-   </para>
-   <tip>
-    <simpara>
-     While replication slots can be useful for streaming replication, it's
-     recommended to monitor for inactive slots as these will cause WAL files to
-     build up indefinitely, possibly leading to server failure.
-    </simpara>
-    <simpara>
-     As an alternative we recommend using EDB's <ulink url="https://www.pgbarman.org/">Barman</ulink>,
-     which offloads WAL management to a separate server, removing the requirement to use a replication
-     slot for each individual standby to reserve WAL. See section <xref linkend="cloning-from-barman"/>
-     for more details on using &repmgr; together with Barman.
-    </simpara>
-   </tip>
- </sect1>
-
- <sect1 id="cloning-cascading" xreflabel="Cloning and cascading replication">
-   <title>Cloning and cascading replication</title>
-
-   <indexterm>
-     <primary>cloning</primary>
-     <secondary>cascading replication</secondary>
-   </indexterm>
-
-   <para>
-    Cascading replication, introduced with PostgreSQL 9.2, enables a standby server
-    to replicate from another standby server rather than directly from the primary,
-    meaning replication changes "cascade" down through a hierarchy of servers. This
-    can be used to reduce load on the primary and minimize bandwidth usage between
-    sites. For more details, see the
-    <ulink url="https://www.postgresql.org/docs/current/warm-standby.html#CASCADING-REPLICATION">
-    PostgreSQL cascading replication documentation</ulink>.
-   </para>
-   <para>
-    &repmgr; supports cascading replication. When cloning a standby,
-    set the command-line parameter <literal>--upstream-node-id</literal> to the
-    <varname>node_id</varname> of the server the standby should connect to, and
-    &repmgr; will create a replication configuration file to point to it. Note
-    that if <literal>--upstream-node-id</literal> is not explicitly provided,
-    &repmgr; will set the standby's replication configuration to
-    point to the primary node.
-   </para>
-   <para>
-    To demonstrate cascading replication, first ensure you have a primary and standby
-    set up as shown in the <xref linkend="quickstart"/>.
-    Then create an additional standby server with <filename>repmgr.conf</filename> looking
-    like this:
-    <programlisting>
-    node_id=3
-    node_name=node3
-    conninfo='host=node3 user=repmgr dbname=repmgr'
-    data_directory='/var/lib/postgresql/data'</programlisting>
-   </para>
-   <para>
-    Clone this standby (using the connection parameters for the existing standby),
-    ensuring <literal>--upstream-node-id</literal> is provide with the <varname>node_id</varname>
-    of the previously created standby (if following the example, this will be <literal>2</literal>):
-    <programlisting>
-    $ repmgr -h node2 -U repmgr -d repmgr -f /etc/repmgr.conf standby clone --upstream-node-id=2
-    NOTICE: using configuration file "/etc/repmgr.conf"
-    NOTICE: destination directory "/var/lib/postgresql/data" provided
-    INFO: connecting to upstream node
-    INFO: connected to source node, checking its state
-    NOTICE: checking for available walsenders on upstream node (2 required)
-    INFO: sufficient walsenders available on upstream node (2 required)
-    INFO: successfully connected to source node
-    DETAIL: current installation size is 29 MB
-    INFO: creating directory "/var/lib/postgresql/data"...
-    NOTICE: starting backup (using pg_basebackup)...
-    HINT: this may take some time; consider using the -c/--fast-checkpoint option
-    INFO: executing: 'pg_basebackup -l "repmgr base backup" -D /var/lib/postgresql/data -h node2 -U repmgr -X stream '
-    NOTICE: standby clone (using pg_basebackup) complete
-    NOTICE: you can now start your PostgreSQL server
-    HINT: for example: pg_ctl -D /var/lib/postgresql/data start</programlisting>
-
-    then register it (note that <literal>--upstream-node-id</literal> must be provided here
-    too):
-    <programlisting>
-     $ repmgr -f /etc/repmgr.conf standby register --upstream-node-id=2
-     NOTICE: standby node "node2" (ID: 2) successfully registered
-    </programlisting>
-   </para>
-   <para>
-    After starting the standby, the cluster will look like this, showing that <literal>node3</literal>
-    is attached to <literal>node2</literal>, not the primary (<literal>node1</literal>).
-    <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster show
-     ID | Name  | Role    | Status    | Upstream | Location | Connection string
-    ----+-------+---------+-----------+----------+----------+--------------------------------------
-     1  | node1 | primary | * running |          | default  | host=node1 dbname=repmgr user=repmgr
-     2  | node2 | standby |   running | node1    | default  | host=node2 dbname=repmgr user=repmgr
-     3  | node3 | standby |   running | node2    | default  | host=node3 dbname=repmgr user=repmgr
-    </programlisting>
-   </para>
-   <tip>
-    <simpara>
-     Under some circumstances when setting up a cascading replication
-     cluster, you may wish to clone a downstream standby whose upstream node
-     does not yet exist. In this case you can clone from the primary (or
-     another upstream node); provide the parameter <literal>--upstream-conninfo</literal>
-     to explicitly set the upstream's <varname>primary_conninfo</varname> string
-     in the replication configuration.
-    </simpara>
-   </tip>
- </sect1>
-
- <sect1 id="cloning-advanced" xreflabel="Advanced cloning options">
-   <title>Advanced cloning options</title>
-   <indexterm>
-     <primary>cloning</primary>
-     <secondary>advanced options</secondary>
-   </indexterm>
-
-   <sect2 id="cloning-advanced-pg-basebackup-options" xreflabel="pg_basebackup options when cloning a standby">
-    <title>pg_basebackup options when cloning a standby</title>
-    <para>
-      As &repmgr; uses <command>pg_basebackup</command> to clone a standby, it's possible to
-      provide additional parameters for <command>pg_basebackup</command> to customise the
-      cloning process.
-    </para>
-
-    <para>
-     By default, <command>pg_basebackup</command> performs a checkpoint before beginning the backup
-     process. However, a normal checkpoint may take some time to complete;
-     a fast checkpoint can be forced with <command><link linkend="repmgr-standby-clone">repmgr standby clone</link></command>'s
-     <literal>-c/--fast-checkpoint</literal> option.
-     Note that this may impact performance of the server being cloned from (typically the primary)
-     so should be used with care.
-    </para>
-    <tip>
-      <simpara>
-        If <application>Barman</application> is set up for the cluster, it's possible to
-        clone the standby directly from Barman, without any impact on the server the standby
-        is being cloned from. For more details see <xref linkend="cloning-from-barman"/>.
-      </simpara>
-    </tip>
-    <para>
-      Other options can be passed to <command>pg_basebackup</command> by including them
-      in the <filename>repmgr.conf</filename> setting <varname>pg_basebackup_options</varname>.
-    </para>
-
-    <para>
-      Not that by default, &repmgr; executes <command>pg_basebackup</command> with <option>-X/--wal-method</option>
-      (PostgreSQL 9.6 and earlier: <option>-X/--xlog-method</option>) set to <literal>stream</literal>.
-      From PostgreSQL 9.6, if replication slots are in use, it will also create a replication slot before
-      running the base backup, and execute <command>pg_basebackup</command> with the
-      <option>-S/--slot</option> option set to the name of the previously created replication slot.
-    </para>
-    <para>
-      These parameters can set by the user in <varname>pg_basebackup_options</varname>, in which case they
-      will override the &repmgr; default values. However normally there's no reason to do this.
-    </para>
-    <para>
-      If using a separate directory to store WAL files, provide the option <literal>--waldir</literal>
-      (<literal>--xlogdir</literal> in PostgreSQL 9.6 and earlier) with the absolute path to the
-      WAL directory. Any WALs generated during the cloning process will be copied here, and
-      a symlink will automatically be created from the main data directory.
-    </para>
-    <tip>
-      <para>
-        The <literal>--waldir</literal> (<literal>--xlogdir</literal>) option,
-        if present in <varname>pg_basebackup_options</varname>, will be honoured by &repmgr;
-        when cloning from Barman (&repmgr; 5.2 and later).
-      </para>
-    </tip>
-    <para>
-     See the <ulink url="https://www.postgresql.org/docs/current/app-pgbasebackup.html">PostgreSQL pg_basebackup documentation</ulink>
-     for more details of available options.
-    </para>
-   </sect2>
-
-   <sect2 id="cloning-advanced-managing-passwords" xreflabel="Managing passwords">
-    <title>Managing passwords</title>
-    <indexterm>
-      <primary>cloning</primary>
-      <secondary>using passwords</secondary>
-    </indexterm>
-
-    <para>
-     If replication connections to a standby's upstream server are password-protected,
-     the standby must be able to provide the password so it can begin streaming replication.
-    </para>
-
-    <para>
-     The recommended way to do this is to store the password in the <literal>postgres</literal> system
-     user's <filename>~/.pgpass</filename> file.  For more information on using the password file, see
-     the documentation section <xref linkend="configuration-password-file"/>.
-    </para>
-
-    <note>
-      <para>
-        If using a <filename>pgpass</filename> file, an entry for the replication user (by default the
-        user who connects to the <literal>repmgr</literal> database) <emphasis>must</emphasis>
-        be provided, with database name set to <literal>replication</literal>, e.g.:
-        <programlisting>
-          node1:5432:replication:repmgr:12345</programlisting>
-      </para>
-    </note>
-
-    <para>
-     If, for whatever reason, you wish to include the password in the replication configuration file,
-     set <varname>use_primary_conninfo_password</varname> to <literal>true</literal> in
-     <filename>repmgr.conf</filename>. This will read a password set in <varname>PGPASSWORD</varname>
-     (but not <filename>~/.pgpass</filename>) and place it into the <varname>primary_conninfo</varname>
-     string in the replication configuration. Note that <varname>PGPASSWORD</varname>
-     will need to be set during any action which causes the replication configuration file to be
-     rewritten, e.g. <xref linkend="repmgr-standby-follow"/>.
-    </para>
-   </sect2>
-
-   <sect2 id="cloning-advanced-replication-user" xreflabel="Separate replication user">
-    <title>Separate replication user</title>
-    <para>
-     In some circumstances it might be desirable to create a dedicated replication-only
-     user (in addition to the user who manages the &repmgr; metadata). In this case,
-     the replication user should be set in <filename>repmgr.conf</filename> via the parameter
-     <varname>replication_user</varname>; &repmgr; will use this value when making
-     replication connections and generating the replication configuration. This
-     value will also be stored in the parameter <literal>repmgr.nodes</literal>
-     table for each node; it no longer needs to be explicitly specified when
-     cloning a node or executing <xref linkend="repmgr-standby-follow"/>.
-    </para>
-   </sect2>
-
-
-   <sect2 id="cloning-advanced-tablespace-mapping" xreflabel="Tablespace mapping">
-    <title>Tablespace mapping</title>
-    <indexterm>
-      <primary>tablespace mapping</primary>
-    </indexterm>
-    <para>
-      &repmgr; provides a <option>tablespace_mapping</option> configuration
-      file option, which will makes it possible to map the tablespace on the source node to
-      a different location on the local node.
-    </para>
-    <para>
-      To use this, add <option>tablespace_mapping</option> to <filename>repmgr.conf</filename>
-      like this:
-<programlisting>
-  tablespace_mapping='/var/lib/pgsql/tblspc1=/data/pgsql/tblspc1'
-</programlisting>
-    </para>
-    <para>
-      where the left-hand value represents the tablespace on the source node,
-      and the right-hand value represents  the tablespace on the standby to be cloned.
-    </para>
-    <para>
-      This parameter can be provided multiple times.
-    </para>
-   </sect2>
-
- </sect1>
-
-
-</chapter>

doc/configuration-file-log-settings.xml

@@ -1,107 +0,0 @@
-<sect1 id="configuration-file-log-settings" xreflabel="log settings">
-  <title>Log settings</title>
-
-  <indexterm>
-    <primary>repmgr.conf</primary>
-    <secondary>log settings</secondary>
-  </indexterm>
-  <indexterm>
-    <primary>log settings</primary>
-    <secondary>configuration in repmgr.conf</secondary>
-  </indexterm>
-
-  <para>
-    By default, &repmgr; and &repmgrd; write log output to
-    <literal>STDERR</literal>. An alternative log destination can be specified
-    (either a file or <literal>syslog</literal>).
-  </para>
-
-  <note>
-    <para>
-      The &repmgr; application itself will continue to write log output to <literal>STDERR</literal>
-      even if another log destination is configured, as otherwise any output resulting from a command
-      line operation will "disappear" into the log.
-    </para>
-    <para>
-      This behaviour can be overriden with the command line option <option>--log-to-file</option>,
-      which will redirect all logging output to the configured log destination. This is recommended
-      when &repmgr; is executed by another application, particularly &repmgrd;,
-      to enable log output generated by the &repmgr; application to be stored for later reference.
-    </para>
-  </note>
-
-  <variablelist>
-
-   <varlistentry id="repmgr-conf-log-level" xreflabel="log_level">
-    <term><varname>log_level</varname> (<type>string</type>)</term>
-    <listitem>
-     <indexterm>
-      <primary><varname>log_level</varname> configuration file parameter</primary>
-     </indexterm>
-     <para>
-       One of <option>DEBUG</option>, <option>INFO</option>, <option>NOTICE</option>,
-       <option>WARNING</option>, <option>ERROR</option>, <option>ALERT</option>, <option>CRIT</option>
-       or <option>EMERG</option>.
-     </para>
-     <para>
-       Default is <option>INFO</option>.
-     </para>
-     <para>
-       Note that <option>DEBUG</option> will produce a substantial amount of log output
-       and should not be enabled in normal use.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="repmgr-conf-log-facility" xreflabel="log_facility">
-    <term><varname>log_facility</varname> (<type>string</type>)
-     <indexterm>
-      <primary><varname>log_facility</varname> configuration file parameter</primary>
-     </indexterm>
-    </term>
-    <listitem>
-     <para>
-       Logging facility: possible values are <option>STDERR</option> (default), or for
-       syslog integration, one of <option>LOCAL0</option>, <option>LOCAL1</option>, <option>...</option>,
-       <option>LOCAL7</option>, <option>USER</option>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="repmgr-conf-log-file" xreflabel="log_file">
-    <term><varname>log_file</varname> (<type>string</type>)
-     <indexterm>
-      <primary><varname>log_file</varname> configuration file parameter</primary>
-     </indexterm>
-    </term>
-    <listitem>
-     <para>
-       If <xref linkend="repmgr-conf-log-facility"/> is set to <option>STDERR</option>, log output
-       can be redirected to the specified file.
-     </para>
-     <para>
-       See <xref linkend="repmgrd-log-rotation"/> for information on configuring log rotation.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="repmgr-conf-log-status-interval" xreflabel="log_status_interval">
-    <term><varname>log_status_interval</varname> (<type>integer</type>)
-     <indexterm>
-      <primary><varname>log_status_interval</varname> configuration file parameter</primary>
-     </indexterm>
-    </term>
-    <listitem>
-     <para>
-       This setting causes &repmgrd; to emit a status log
-       line at the specified interval (in seconds, default <literal>300</literal>)
-       describing &repmgrd;'s current state, e.g.:
-     </para>
-     <programlisting>
-      [2018-07-12 00:47:32] [INFO] monitoring connection to upstream node "node1" (ID: 1)</programlisting>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
-</sect1>

doc/configuration-file-optional-settings.xml

@@ -1,189 +0,0 @@
-<sect1 id="configuration-file-optional-settings" xreflabel="optional configuration file settings">
-
-  <title>Optional configuration file settings</title>
-
-  <indexterm>
-    <primary>repmgr.conf</primary>
-    <secondary>optional settings</secondary>
-  </indexterm>
-
-  <note>
-    <simpara>
-      This section documents a subset of optional configuration settings; for a full
-      and annotated view of all configuration options see the
-      <ulink url="https://raw.githubusercontent.com/EnterpriseDB/repmgr/master/repmgr.conf.sample">sample repmgr.conf file</ulink>
-    </simpara>
-  </note>
-
-  <variablelist>
-
-
-    <varlistentry id="repmgr-conf-config-directory" xreflabel="config_directory">
-      <term><varname>config_directory</varname> (<type>string</type>)
-        <indexterm>
-          <primary><varname>config_directory</varname> configuration file parameter</primary>
-        </indexterm>
-      </term>
-      <listitem>
-        <para>
-          If PostgreSQL configuration files are located outside the data
-	  directory, specify the directory where the main
-	  <filename>postgresql.conf</filename> file is located.
-        </para>
-        <para>
-          This enables explicit provision of an external configuration file
-          directory, which if set will be passed to <command>pg_ctl</command> as the
-          <option>-D</option> parameter. Otherwise <command>pg_ctl</command> will
-          default to using the data directory, which will cause some operations
-          to fail if the configuration files are not present there.
-        </para>
-        <note>
-          <para>
-           This is implemented primarily for feature completeness and for
-           development/testing purposes. Users who have installed &repmgr; from
-           a package should <emphasis>not</emphasis> rely on  to stop/start/restart PostgreSQL,
-           instead they should set the appropriate <option>service_..._command</option>
-           for their operating system. For more details see
-           <xref linkend="configuration-file-service-commands"/>.
-          </para>
-        </note>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry id="repmgr-conf-replication-user" xreflabel="replication_user">
-      <term><varname>replication_user</varname> (<type>string</type>)
-        <indexterm>
-          <primary><varname>replication_user</varname> configuration file parameter</primary>
-        </indexterm>
-      </term>
-      <listitem>
-        <para>
-          PostgreSQL user to make replication connections with.
-          If not set defaults, to the user defined in <xref linkend="repmgr-conf-conninfo"/>.
-        </para>
-      </listitem>
-    </varlistentry>
-
-
-
-    <varlistentry id="repmgr-conf-replication-type" xreflabel="replication_type">
-      <term><varname>replication_type</varname> (<type>string</type>)
-        <indexterm>
-          <primary><varname>replication_type</varname> configuration file parameter</primary>
-        </indexterm>
-      </term>
-      <listitem>
-        <para>
-          Must be <literal>physical</literal> (the default).
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry id="repmgr-conf-location" xreflabel="location">
-      <term><varname>location</varname> (<type>string</type>)
-        <indexterm>
-          <primary><varname>location</varname> configuration file parameter</primary>
-        </indexterm>
-      </term>
-      <listitem>
-        <para>
-          An arbitrary string defining the location of the node; this
-	  is used during failover to check visibility of the
-	  current primary node.
-        </para>
-        <para>
-          For more details see <xref linkend="repmgrd-network-split"/>.
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry id="repmgr-conf-use-replication-slots" xreflabel="use_replication_slots">
-      <term><varname>use_replication_slots</varname> (<type>boolean</type>)
-        <indexterm>
-          <primary><varname>use_replication_slots</varname> configuration file parameter</primary>
-        </indexterm>
-      </term>
-      <listitem>
-        <para>
-          Whether to use physical replication slots.
-        </para>
-        <note>
-          <para>
-	    When using replication slots,
-	    <varname>max_replication_slots</varname> should be configured for
-	    at least the number of standbys which will connect
-	    to the primary.
-          </para>
-        </note>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry id="repmgr-conf-ssh-options" xreflabel="ssh_options">
-      <term><varname>ssh_options</varname> (<type>string</type>)
-        <indexterm>
-          <primary><varname>ssh_options</varname> configuration file parameter</primary>
-        </indexterm>
-      </term>
-      <listitem>
-        <para>
-          Options to append to the <command>ssh</command> command when executed
-          by &repmgr;.
-        </para>
-        <para>
-          We recommend adding <literal>-q</literal> to suppress any superfluous
-          SSH chatter such as login banners, and also an explicit
-          <option>ConnectTimeout</option> value,
-          e.g.:
-<programlisting>
-ssh_options='-q -o ConnectTimeout=10'</programlisting>
-        </para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry id="repmgr-conf-pg-bindir" xreflabel="pg_bindir">
-      <term><varname>pg_bindir</varname> (<type>string</type>)
-        <indexterm>
-          <primary><varname>pg_bindir</varname> configuration file parameter</primary>
-        </indexterm>
-      </term>
-      <listitem>
-        <para>
-          Path to the PostgreSQL binary directory (location of <application>pg_ctl</application>,
-          <application>pg_basebackup</application> etc.). Only required
-	  if these are not in the system <varname>PATH</varname>.
-        </para>
-        <tip>
-          <para>
-            When &repmgr; is executed via <application>SSH</application> (e.g. when running
-            <command><link linkend="repmgr-standby-switchover">repmgr standby switchover</link></command>,
-            <command><link linkend="repmgr-cluster-matrix">repmgr cluster matrix</link></command> or
-            <command><link linkend="repmgr-cluster-crosscheck">repmgr cluster crosscheck</link></command>,
-            or if it is executed as cronjob), a login shell will not be used and only the
-            default system <varname>PATH</varname> will be set. Therefore it's recommended to set
-            <varname>pg_bindir</varname> so &repmgr; can correctly invoke binaries on a remote
-            system and avoid potential path issues.
-          </para>
-        </tip>
-
-        <para>
-          Debian/Ubuntu users: you will probably need to  set this to the directory where
-          <application>pg_ctl</application> is located, e.g. <filename>/usr/lib/postgresql/9.6/bin/</filename>.
-        </para>
-        <para>
-          <emphasis>NOTE</emphasis>: <varname>pg_bindir</varname> is only used when &repmgr; directly
-	  executes PostgreSQL binaries; any user-defined scripts
-	  <emphasis>must</emphasis> be specified with the full path.
-        </para>
-
-      </listitem>
-    </varlistentry>
-  </variablelist>
-
-  <tip>
-    <simpara>
-      See the <ulink url="https://raw.githubusercontent.com/EnterpriseDB/repmgr/master/repmgr.conf.sample">sample repmgr.conf file</ulink>
-      for a full and annotated view of all configuration options.
-    </simpara>
-  </tip>
-
-</sect1>

doc/configuration-file-required-settings.xml

@@ -1,104 +0,0 @@
-<sect1 id="configuration-file-settings" xreflabel="required configuration file settings">
-
- <title>Required configuration file settings</title>
-
-  <indexterm>
-    <primary>repmgr.conf</primary>
-    <secondary>required settings</secondary>
-  </indexterm>
-
- <para>
-   Each <filename>repmgr.conf</filename> file must contain the following parameters:
- </para>
- <para>
-  <variablelist>
-   <varlistentry id="repmgr-conf-node-id" xreflabel="node_id">
-    <term><varname>node_id</varname> (<type>int</type>)
-     <indexterm>
-      <primary><varname>node_id</varname> configuration file parameter</primary>
-     </indexterm>
-    </term>
-    <listitem>
-     <para>
-      A unique integer greater than zero which identifies the node.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="repmgr-conf-node-name" xreflabel="node_name">
-    <term><varname>node_name</varname> (<type>string</type>)
-     <indexterm>
-      <primary><varname>node_name</varname> configuration file parameter</primary>
-     </indexterm>
-    </term>
-    <listitem>
-     <para>
-       An arbitrary (but unique) string; we recommend using the server's hostname
-       or another identifier unambiguously associated with the server to avoid
-       confusion. Avoid choosing names which reflect the node's current role,
-       e.g. <varname>primary</varname> or <varname>standby1</varname>
-       as roles can change and if you end up in a solution where the current primary is
-       called <varname>standby1</varname> (for example), things will be confusing
-       to say the least.
-     </para>
-     <para>
-       The string's maximum length is 63 characters and it should
-       contain only printable ASCII characters.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="repmgr-conf-conninfo" xreflabel="conninfo">
-    <term><varname>conninfo</varname> (<type>string</type>)
-     <indexterm>
-      <primary><varname>conninfo</varname> configuration file parameter</primary>
-     </indexterm>
-    </term>
-    <listitem>
-     <para>
-      Database connection information as a conninfo string.
-      All servers in the cluster must be able to connect to
-      the local node using this string.
-     </para>
-     <para>
-       For details on conninfo strings, see section <ulink
-       url="https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING">Connection Strings</ulink>
-        in the PosgreSQL documentation.
-     </para>
-     <para>
-        If repmgrd is in use, consider explicitly setting
-        <varname>connect_timeout</varname> in the <varname>conninfo</varname>
-        string to determine the length of time which elapses before a network
-        connection attempt is abandoned; for details see <ulink
-        url="https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-CONNECT-TIMEOUT">
-        the PostgreSQL documentation</ulink>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry id="repmgr-conf-data-directory" xreflabel="data_directory">
-    <term><varname>data_directory</varname> (<type>string</type>)</term>
-    <listitem>
-      <indexterm>
-        <primary><varname>data_directory</varname> configuration file parameter</primary>
-      </indexterm>
-
-     <para>
-       The node's data directory. This is needed by repmgr
-       when performing operations when the PostgreSQL instance
-       is not running and there's no other way of determining
-       the data directory.
-     </para>
-    </listitem>
-   </varlistentry>
-
-
-  </variablelist>
- </para>
-
- <para>
-   See <xref linkend="configuration-file-optional-settings"/> for further configuration options.
- </para>
-
-
-</sect1>

doc/configuration-file-service-commands.xml

@@ -1,133 +0,0 @@
-<sect1 id="configuration-file-service-commands" xreflabel="service command settings">
-  <title>Service command settings</title>
-
-  <indexterm>
-    <primary>repmgr.conf</primary>
-    <secondary>service command settings</secondary>
-  </indexterm>
-  <indexterm>
-    <primary>service command settings</primary>
-    <secondary>configuration in repmgr.conf</secondary>
-  </indexterm>
-
-  <para>
-    In some circumstances, &repmgr; (and &repmgrd;) need to
-    be able to stop, start or restart PostgreSQL. &repmgr; commands which need to do this
-    include <link linkend="repmgr-standby-follow"><command>repmgr standby follow</command></link>,
-    <link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link> and
-    <link linkend="repmgr-node-rejoin"><command>repmgr node rejoin</command></link>.
-  </para>
-  <para>
-    By default, &repmgr; will use PostgreSQL's <command>pg_ctl</command> utility to control the PostgreSQL
-    server. However this can lead to various problems, particularly when PostgreSQL has been
-    installed from packages, and especially so if <application>systemd</application> is in use.
-  </para>
-
-
-  <note>
-    <para>
-      If using <application>systemd</application>, ensure you have <varname>RemoveIPC</varname> set to <literal>off</literal>.
-      See the <ulink url="https://www.postgresql.org/docs/current/index.html">PostgreSQL documentation</ulink> section
-      <ulink url="https://www.postgresql.org/docs/current/kernel-resources.html#SYSTEMD-REMOVEIPC">systemd RemoveIPC</ulink>
-      and also the <ulink url="https://wiki.postgresql.org/wiki/Systemd">systemd</ulink>
-      entry in the <ulink url="https://wiki.postgresql.org/wiki/Main_Page">PostgreSQL wiki</ulink> for details.
-    </para>
-  </note>
-
-
-  <para>
-    With this in mind, we recommend to <emphasis>always</emphasis> configure &repmgr; to use the
-    available system service commands.
-  </para>
-
-  <para>
-    To do this, specify the appropriate command for each action
-    in <filename>repmgr.conf</filename> using the following configuration
-    parameters:
-    <programlisting>
-    service_start_command
-    service_stop_command
-    service_restart_command
-    service_reload_command</programlisting>
-  </para>
-
-  <note>
-    <para>
-      &repmgr; will not apply <option>pg_bindir</option> when executing any of these commands;
-      these can be user-defined scripts so must always be specified with the full path.
-    </para>
-  </note>
-
-  <note>
-    <para>
-      It's also possible to specify a <varname>service_promote_command</varname>.
-      This is intended for systems which provide a package-level promote command,
-      such as Debian's <application>pg_ctlcluster</application>, to promote the
-      PostgreSQL from standby to primary.
-    </para>
-    <para>
-      If your packaging system does not provide such a command, it can be left empty,
-      and &repmgr; will generate the appropriate `pg_ctl ... promote` command.
-    </para>
-    <para>
-      Do not confuse this with <varname>promote_command</varname>, which is used
-      by &repmgrd; to execute <xref linkend="repmgr-standby-promote"/>.
-    </para>
-  </note>
-
-  <para>
-    To confirm which command &repmgr; will execute for each action, use
-    <command><link linkend="repmgr-node-service">repmgr node service --list-actions --action=...</link></command>, e.g.:
-    <programlisting>
-      repmgr -f /etc/repmgr.conf node service --list-actions --action=stop
-      repmgr -f /etc/repmgr.conf node service --list-actions --action=start
-      repmgr -f /etc/repmgr.conf node service --list-actions --action=restart
-      repmgr -f /etc/repmgr.conf node service --list-actions --action=reload</programlisting>
-  </para>
-
-  <para>
-     These commands will be executed by the system user which &repmgr; runs as (usually <literal>postgres</literal>)
-     and will probably require passwordless sudo access to be able to execute the command.
-  </para>
-  <para>
-    For example, using <application>systemd</application> on CentOS 7, the service commands can be
-    set as follows:
-    <programlisting>
-      service_start_command   = 'sudo systemctl start postgresql-9.6'
-      service_stop_command    = 'sudo systemctl stop postgresql-9.6'
-      service_restart_command = 'sudo systemctl restart postgresql-9.6'
-      service_reload_command  = 'sudo systemctl reload postgresql-9.6'</programlisting>
-    and <filename>/etc/sudoers</filename> should be set as follows:
-    <programlisting>
-      Defaults:postgres !requiretty
-      postgres ALL = NOPASSWD: /usr/bin/systemctl stop postgresql-9.6, \
-        /usr/bin/systemctl start postgresql-9.6, \
-        /usr/bin/systemctl restart postgresql-9.6, \
-        /usr/bin/systemctl reload postgresql-9.6</programlisting>
-  </para>
-
-  <important>
-    <indexterm>
-      <primary>pg_ctlcluster</primary>
-      <secondary>service command settings</secondary>
-    </indexterm>
-    <para>
-      Debian/Ubuntu users: instead of calling <command>sudo systemctl</command> directly, use
-      <command>sudo pg_ctlcluster</command>, e.g.:
-    <programlisting>
-      service_start_command   = 'sudo pg_ctlcluster 9.6 main start'
-      service_stop_command    = 'sudo pg_ctlcluster 9.6 main stop'
-      service_restart_command = 'sudo pg_ctlcluster 9.6 main restart'
-      service_reload_command  = 'sudo pg_ctlcluster 9.6 main reload'</programlisting>
-      and set <filename>/etc/sudoers</filename> accordingly.
-    </para>
-    <para>
-      While <command>pg_ctlcluster</command> will work when executed as user <literal>postgres</literal>,
-      it's strongly recommended to use <command>sudo pg_ctlcluster</command> on <application>systemd</application>
-      systems, to ensure <application>systemd</application> has a correct picture of
-      the PostgreSQL application state.
-    </para>
-
-  </important>
-
-</sect1>

doc/configuration-file.xml

@@ -1,315 +0,0 @@
-<sect1 id="configuration-file" xreflabel="configuration file">
-
-  <title>Configuration file</title>
-
-  <indexterm>
-    <primary>repmgr.conf</primary>
-  </indexterm>
-
-  <indexterm>
-    <primary>configuration</primary>
-    <secondary>repmgr.conf</secondary>
-  </indexterm>
-
-  <para>
-    <application>repmgr</application> and &repmgrd;
-    use a common configuration file, by default called
-    <filename>repmgr.conf</filename> (although any name can be used if explicitly specified).
-    <filename>repmgr.conf</filename> must contain a number of required parameters, including
-    the database connection string for the local node and the location
-    of its data directory; other values will be inferred from defaults if
-    not explicitly supplied. See section <xref linkend="configuration-file-settings"/>
-    for more details.
-  </para>
-
-  <sect2 id="configuration-file-format" xreflabel="configuration file format">
-
-    <title>Configuration file format</title>
-
-    <indexterm>
-      <primary>repmgr.conf</primary>
-      <secondary>format</secondary>
-    </indexterm>
-
-
-
-    <para>
-      <filename>repmgr.conf</filename> is a plain text file with one parameter/value
-      combination per line.
-    </para>
-    <para>
-      Whitespace is insignificant (except within a quoted parameter value) and blank lines are ignored.
-      Hash marks (<literal>#</literal>) designate the remainder of the line as a comment.
-      Parameter values that are not simple identifiers or numbers should be single-quoted.
-    </para>
-    <para>
-      To embed a single quote in a parameter value, write either two quotes (preferred) or backslash-quote.
-    </para>
-
-    <para>
-      Example of a valid <filename>repmgr.conf</filename> file:
-      <programlisting>
-# repmgr.conf
-
-node_id=1
-node_name= node1
-conninfo ='host=node1 dbname=repmgr user=repmgr connect_timeout=2'
-data_directory = '/var/lib/pgsql/12/data'</programlisting>
-
-    </para>
-
-    <note>
-      <para>
-        Beginning with <link linkend="release-5.0">repmgr 5.0</link>, configuration
-        file parsing has been tightened up and now matches the way PostgreSQL
-        itself parses configuration files.
-      </para>
-      <para>
-        This means <filename>repmgr.conf</filename> files used with earlier &repmgr;
-        versions may need slight modification before they can be used with &repmgr; 5
-        and later.
-      </para>
-      <para>
-        The main change is that &repmgr; requires most string values to be
-        enclosed in single quotes. For example, this was previously valid:
-          <programlisting>
-conninfo=host=node1 user=repmgr dbname=repmgr connect_timeout=2</programlisting>
-          but must now be changed to:
-          <programlisting>
-conninfo='host=node1 user=repmgr dbname=repmgr connect_timeout=2'</programlisting>
-      </para>
-    </note>
-
-
-    <sect3 id="configuration-file-include-directives" xreflabel="configuration file include directives">
-
-      <title>Configuration file include directives</title>
-
-      <indexterm>
-        <primary>repmgr.conf</primary>
-        <secondary>include directives</secondary>
-      </indexterm>
-      <para>
-        From &repmgr; 5.2, the configuration file can contain the following include directives:
-        <itemizedlist spacing="compact" mark="bullet">
-          <listitem>
-            <simpara>
-              <option>include</option>: include the specified file,
-              either as an absolute path or path relative to the current file
-            </simpara>
-          </listitem>
-
-          <listitem>
-            <simpara>
-              <option>include_if_exists</option>: include the specified file.
-              The file is specified as an absolute path or path relative to the current file.
-              However, if it does not exist, an error will not be raised.
-            </simpara>
-          </listitem>
-
-          <listitem>
-            <simpara>
-              <option>include_dir</option>: include files in the specified directory
-              which have the <filename>.conf</filename> suffix.
-              The directory is specified either as an absolute path or path
-              relative to the current file
-            </simpara>
-          </listitem>
-
-        </itemizedlist>
-      </para>
-      <para>
-        These behave in exactly the same way as the PostgreSQL configuration file processing;
-        see the <ulink url="https://www.postgresql.org/docs/current/config-setting.html#CONFIG-INCLUDES">PostgreSQL documentation</ulink>
-        for additional details.
-      </para>
-    </sect3>
-
-  </sect2>
-
-
-  <sect2 id="configuration-file-items" xreflabel="configuration file items">
-
-    <title>Configuration file items</title>
-    <para>
-      The following sections document some sections of the configuration file:
-       <itemizedlist>
-          <listitem>
-            <simpara>
-              <xref linkend="configuration-file-settings"/>
-            </simpara>
-          </listitem>
-
-          <listitem>
-            <simpara>
-              <xref linkend="configuration-file-optional-settings"/>
-            </simpara>
-          </listitem>
-
-          <listitem>
-            <simpara>
-              <xref linkend="configuration-file-log-settings"/>
-            </simpara>
-          </listitem>
-
-
-          <listitem>
-            <simpara>
-              <xref linkend="configuration-file-service-commands"/>
-            </simpara>
-          </listitem>
-
-       </itemizedlist>
-
-    </para>
-    <para>
-      For a full list of annotated configuration items, see the file
-      <ulink url="https://raw.githubusercontent.com/EnterpriseDB/repmgr/master/repmgr.conf.sample">repmgr.conf.sample</ulink>.
-    </para>
-    <para>
-      For &repmgrd;-specific settings, see <xref linkend="repmgrd-configuration"/>.
-    </para>
-
-    <note>
-      <para>
-        The following parameters in the configuration file can be overridden with
-        command line options:
-        <itemizedlist>
-          <listitem>
-            <simpara>
-              <literal>-L/--log-level</literal> overrides <literal>log_level</literal> in
-              <filename>repmgr.conf</filename>
-            </simpara>
-          </listitem>
-          <listitem>
-            <simpara>
-              <literal>-b/--pg_bindir</literal> overrides <literal>pg_bindir</literal> in
-              <filename>repmgr.conf</filename>
-            </simpara>
-          </listitem>
-        </itemizedlist>
-      </para>
-    </note>
-
-  </sect2>
-
-  <sect2 id="configuration-file-location" xreflabel="configuration file location">
-  <title>Configuration file location</title>
-
-  <indexterm>
-    <primary>repmgr.conf</primary>
-    <secondary>location</secondary>
-  </indexterm>
-
-
-  <para>
-   The configuration file will be searched for in the following locations:
-   <itemizedlist spacing="compact" mark="bullet">
-    <listitem>
-     <para>a configuration file specified by the <literal>-f/--config-file</literal> command line option</para>
-    </listitem>
-    <listitem>
-     <para>
-      a location specified by the package maintainer (if <application>repmgr</application>
-      as installed from a package and the package maintainer has specified the configuration
-      file location)
-     </para>
-    </listitem>
-    <listitem>
-     <para><filename>repmgr.conf</filename> in the local directory</para>
-    </listitem>
-    <listitem>
-      <para><filename>/etc/repmgr.conf</filename></para>
-    </listitem>
-    <listitem>
-     <para>the directory reported by <application>pg_config --sysconfdir</application></para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-    In examples provided in this documentation, it is assumed the configuration file is located
-    at <filename>/etc/repmgr.conf</filename>. If &repmgr; is installed from a package, the
-    configuration file will probably be located at another location specified by the packager;
-    see appendix <xref linkend="appendix-packages"/> for configuration file locations in
-    different packaging systems.
-  </para>
-
-  <para>
-   Note that if a file is explicitly specified with <literal>-f/--config-file</literal>,
-   an error will be raised if it is not found or not readable, and no attempt will be made to
-   check default locations; this is to prevent <application>repmgr</application> unexpectedly
-   reading the wrong configuration file.
-  </para>
-
-  <note>
-    <para>
-      If providing the configuration file location with <literal>-f/--config-file</literal>,
-      avoid using a relative path, particularly when executing <xref linkend="repmgr-primary-register"/>
-      and <xref linkend="repmgr-standby-register"/>, as &repmgr; stores the configuration file location
-      in the repmgr metadata for use when &repmgr; is executed remotely (e.g. during
-      <xref linkend="repmgr-standby-switchover"/>). &repmgr; will attempt to convert the
-      a relative path into an absolute one, but this may not be the same as the path you
-      would explicitly provide (e.g. <filename>./repmgr.conf</filename> might be converted
-      to <filename>/path/to/./repmgr.conf</filename>, whereas you'd normally write
-      <filename>/path/to/repmgr.conf</filename>).
-    </para>
-   </note>
-  </sect2>
-
-  <sect2 id="configuration-file-postgresql-major-upgrades" xreflabel="configuration file and PostgreSQL major version upgrades">
-    <title>Configuration file and PostgreSQL major version upgrades</title>
-
-    <indexterm>
-      <primary>repmgr.conf</primary>
-      <secondary>PostgreSQL major version upgrades</secondary>
-    </indexterm>
-
-    <para>
-      When upgrading the PostgreSQL cluster to a new major version, <filename>repmgr.conf</filename>
-      will probably needed to be updated.
-    </para>
-    <para>
-      Usually <option>pg_bindir</option> and <option>data_directory</option> will need to be modified,
-      particularly if the default package locations are used, as these usually change.
-    </para>
-
-     <para>
-       It's also possible the location of <filename>repmgr.conf</filename> itself will change
-       (e.g. from <filename>/etc/repmgr/11/repmgr.conf</filename> to <filename>/etc/repmgr/12/repmgr.conf</filename>).
-       This is stored as part of the &repmgr; metadata and is used by &repmgr; to execute &repmgr; remotely
-       (e.g. during a <link linkend="performing-switchover">switchover operation</link>).
-     </para>
-     <para>
-       If the content and/or location of <filename>repmgr.conf</filename> has changed, the &repmgr; metadata
-       needs to be updated to reflect this. The &repmgr; metadata can be updated on each node with:
-       <itemizedlist spacing="compact" mark="bullet">
-         <listitem>
-           <simpara>
-             <link linkend="repmgr-primary-register">
-               <command>repmgr primary register --force -f /path/to/repmgr.conf</command>
-             </link>
-           </simpara>
-         </listitem>
-
-         <listitem>
-           <simpara>
-             <link linkend="repmgr-standby-register">
-               <command>repmgr standby register --force -f /path/to/repmgr.conf</command>
-             </link>
-           </simpara>
-         </listitem>
-
-
-         <listitem>
-           <simpara>
-             <link linkend="repmgr-witness-register">
-               <command>repmgr witness register --force -f /path/to/repmgr.conf -h primary_host</command>
-             </link>
-           </simpara>
-         </listitem>
-       </itemizedlist>
-     </para>
-
-   </sect2>
- </sect1>

doc/configuration-password-management.xml

@@ -1,175 +0,0 @@
-<sect1 id="configuration-password-management" xreflabel="password management">
-
-  <title>Password Management</title>
-  <indexterm>
-    <primary>passwords</primary>
-  </indexterm>
-
-  <sect2 id="configuration-password-management-options" xreflabel="password management options">
-  <title>Password Management Options</title>
-  <indexterm>
-    <primary>passwords</primary>
-    <secondary>options for managing</secondary>
-  </indexterm>
-
-  <para>
-    For security purposes it's desirable to protect database access using a password.
-  </para>
-  <para>
-    PostgreSQL has three ways of providing a password:
-    <itemizedlist spacing="compact" mark="bullet">
-
-       <listitem>
-         <simpara>
-           including the password in the <option>conninfo</option> string
-           (e.g. &quot;<literal>host=node1 dbname=repmgr user=repmgr password=foo</literal>&quot;)
-         </simpara>
-       </listitem>
-
-       <listitem>
-         <simpara>
-           exporting the password as an environment variable (<envar>PGPASSWORD</envar>)
-         </simpara>
-       </listitem>
-
-       <listitem>
-         <simpara>
-           storing the password in a dedicated password file
-         </simpara>
-       </listitem>
-    </itemizedlist>
-  </para>
-  <para>
-    We strongly advise against including the password in the <option>conninfo</option> string, as
-    this will result in the database password being exposed in various places, including in the
-    <filename>repmgr.conf</filename> file, the <literal>repmgr.nodes</literal> table, any output
-    generated by &repmgr; which lists the node <option>conninfo</option> strings (e.g.
-    <link linkend="repmgr-cluster-show">repmgr cluster show</link>) and in the &repmgr; log file,
-    particularly at <option>log_level=DEBUG</option>.
-  </para>
-  <note>
-    <para>
-      Currently &repmgr; does not fully support use of the <option>password</option> option in the
-      <option>conninfo</option> string.
-    </para>
-  </note>
-  <para>
-    Exporting the password as an environment variable (<envar>PGPASSWORD</envar>) is considered
-    less insecure, but the PostgreSQL documentation explicitly recommends against doing this:
-   <blockquote>
-     <attribution><ulink url="https://www.postgresql.org/docs/current/libpq-envars.html">Environment Variables</ulink></attribution>
-     <para>
-       <envar>PGPASSWORD</envar> behaves the same as the <option>password</option>
-       connection parameter. Use of this environment variable
-       is not recommended for security reasons, as some operating systems
-       allow non-root users to see process environment variables via
-       <application>ps</application>; instead consider using a password file.
-     </para>
-    </blockquote>
-
-  </para>
-  <para>
-    The most secure option for managing passwords is to use a dedicated password file; see the following
-    section for more details.
-  </para>
-
-  </sect2>
-
-  <sect2 id="configuration-password-file" xreflabel="password file">
-    <title>Using a password file</title>
-    <indexterm>
-      <primary>pgpass</primary>
-    </indexterm>
-
-    <indexterm>
-      <primary>.pgpass</primary>
-    </indexterm>
-
-    <indexterm>
-      <primary>passwords</primary>
-      <secondary>using a password file</secondary>
-    </indexterm>
-
-    <para>
-      The most secure way of storing passwords is in a password file,
-      which by default is <filename>~/.pgpass</filename>. This file
-      can only be read by the system user who owns the file, and
-      PostgreSQL will refuse to use the file unless read/write
-      permissions are restricted to the file owner. The password(s)
-      contained in the file will not be directly accessed by
-      &repmgr; (or any other libpq-based client software such as <application>psql</application>).
-    </para>
-    <para>
-       For full details see the
-       <ulink url="https://www.postgresql.org/docs/current/libpq-pgpass.html">PostgreSQL password file documentation</ulink>.
-    </para>
-    <para>
-      For use with &repmgr;, the <filename>~/.pgpass</filename> must two entries for each
-      node in the replication cluster: one for the &repmgr; user who accesses the &repmgr; metadatabase,
-      and one for replication connections (regardless of whether a dedicated replication user is used).
-      The file must be present on each node in the replication cluster.
-    </para>
-    <para>
-      A <filename>~/.pgpass</filename> file for a 3-node cluster where the <literal>repmgr</literal> database user
-      is used for both for accessing the  &repmgr; metadatabase and for replication connections would look like this:
-      <programlisting>
-node1:5432:repmgr:repmgr:foo
-node1:5432:replication:repmgr:foo
-node2:5432:repmgr:repmgr:foo
-node2:5432:replication:repmgr:foo
-node3:5432:repmgr:repmgr:foo
-node3:5432:replication:repmgr:foo</programlisting>
-      If a dedicated replication user (here: <literal>repluser</literal>) is in use, the file would look like this:
-      <programlisting>
-node1:5432:repmgr:repmgr:foo
-node1:5432:replication:repluser:foo
-node2:5432:repmgr:repmgr:foo
-node2:5432:replication:repluser:foo
-node3:5432:repmgr:repmgr:foo
-node3:5432:replication:repluser:foo</programlisting>
-      If you are planning to use the <option>-S</option>/<option>--superuser</option> option,
-      there must also be an entry enabling the superuser to connect to the &repmgr; database.
-      Assuming the superuser is <literal>postgres</literal>, the file would look like this:
-        <programlisting>
-node1:5432:repmgr:repmgr:foo
-node1:5432:repmgr:postgres:foo
-node1:5432:replication:repluser:foo
-node2:5432:repmgr:repmgr:foo
-node2:5432:repmgr:postgres:foo
-node2:5432:replication:repluser:foo
-node3:5432:repmgr:repmgr:foo
-node3:5432:repmgr:postgres:foo
-node3:5432:replication:repluser:foo</programlisting>
-    </para>
-
-    <para>
-      The <filename>~/.pgpass</filename> file can be simplified with the use of wildcards if
-      there is no requirement to restrict provision of passwords to particular hosts, ports
-      or databases. The preceding file could then be formatted like this:
-        <programlisting>
-*:*:*:repmgr:foo
-*:*:*:postgres:foo
-</programlisting>
-    </para>
-
-    <note>
-      <para>
-        It's possible to specify an alternative location for the <filename>~/.pgpass</filename> file, either via
-        the environment variable <envar>PGPASSFILE</envar>, or (from PostgreSQL 9.6) using the
-        <varname>passfile</varname> parameter in connection strings.
-      </para>
-      <para>
-        If using the <varname>passfile</varname> parameter, it's essential to ensure the file is in the same
-        location on all nodes, as when connecting to a remote node, the file referenced is the one on the
-        local node.
-      </para>
-      <para>
-        Additionally, you <emphasis>must</emphasis> specify the passfile location in <filename>repmgr.conf</filename>
-        with the <option>passfile</option> option so &repmgr; can write the correct path when creating the
-        <option>primary_conninfo</option> parameter for replication configuration on standbys.
-      </para>
-    </note>
-
-  </sect2>
-
-</sect1>

doc/configuration-permissions.xml

@@ -1,200 +0,0 @@
-<sect1 id="configuration-permissions" xreflabel="Database user permissions">
-  <title>repmgr database user permissions</title>
-
-  <indexterm>
-    <primary>configuration</primary>
-    <secondary>database user permissions</secondary>
-  </indexterm>
-
-  <para>
-    If the &repmgr; database user (the PostgreSQL user defined in the
-    <varname>conninfo</varname> setting is a superuser, no further user permissions need
-    to be granted.
-  </para>
-
-  <sect2 id="configuration-permissions-no-superuser" xreflabel="Non-super user permissions">
-    <title>repmgr user as a non-superuser</title>
-    <para>
-      In principle the &repmgr; database user does not need to be a superuser.
-      In this case the &repmgr; will need to be granted execution permissions on certain
-      functions, and membership of certain roles. However be aware that &repmgr; does
-      expect to be able to execute certain commands which are restricted to superusers;
-      in this case either a superuser must be specified with the <option>-S</option>/<option>--superuser</option>
-      (where available) option, or the corresponding action should be executed manually as a superuser.
-    </para>
-    <para>
-      The following sections describe the actions needed to use &repmgr; with a non-superuser,
-      and relevant caveats.
-    </para>
-    <sect3 id="configuration-permissions-replication" xreflabel="Replication role">
-      <title>Replication role</title>
-      <para>
-        &repmgr; requires a database user with the <literal>REPLICATION</literal> role
-        to be able to create a replication connection and (if configured) to administer
-        replication slots.
-      </para>
-      <para>
-        By default this is the database user defined in the <varname>conninfo</varname>
-        setting. This user can be:
-        <itemizedlist spacing="compact" mark="bullet">
-          <listitem>
-            <simpara>
-              a superuser
-            </simpara>
-          </listitem>
-          <listitem>
-            <simpara>
-              a non-superuser with the <literal>REPLICATION</literal> role
-            </simpara>
-          </listitem>
-          <listitem>
-            <simpara>
-              another user defined in the <filename>repmgr.conf</filename> parameter <varname>replication_user</varname> with the <literal>REPLICATION</literal> role
-            </simpara>
-          </listitem>
-        </itemizedlist>
-      </para>
-    </sect3>
-
-    <sect3 id="configuration-permissions-roles" xreflabel="Database roles for non-superusers">
-      <title>Database roles</title>
-      <para>
-        A non-superuser &repmgr; database user should be a member of the following
-        <ulink url="https://www.postgresql.org/docs/current/predefined-roles.html">predefined roles</ulink>
-        (PostgreSQL 10 and later):
-        <itemizedlist spacing="compact" mark="bullet">
-          <listitem>
-            <simpara>
-              <varname>pg_read_all_stats</varname>
-              (to read the <varname>status</varname> column of <literal>pg_stat_replication</literal>
-              and execute <function>pg_database_size()</function> on all databases)
-            </simpara>
-          </listitem>
-          <listitem>
-            <simpara>
-              <varname>pg_read_all_settings</varname> (to access the <varname>data_directory</varname> setting)
-            </simpara>
-          </listitem>
-        </itemizedlist>
-        Alternatively the meta-role <varname>pg_monitor</varname> can be granted, which includes membership
-        of the above predefined roles.
-      </para>
-      <para>
-        PostgreSQL 15 introduced the <varname>pg_checkpoint</varname> predefined role which allows a 
-        non-superuser &repmgr; database user to perform a CHECKPOINT command.
-      </para>
-      <para>
-        Membership of these roles can be granted with e.g. <command>GRANT pg_read_all_stats TO repmgr</command>.
-      </para>
-      <para>
-        Users of PostgreSQL 9.6 or earlier should upgrade to a supported PostgreSQL version, or provide
-        the <option>-S</option>/<option>--superuser</option> where available.
-      </para>
-    </sect3>
-
-    <sect3 id="configuration-permissions-extension" xreflabel="Extension creation">
-      <title>Extension creation</title>
-      <para>
-        &repmgr; requires that the database defined in the <varname>conninfo</varname>
-        setting contains the <literal>repmgr</literal> extension. The database user defined in the
-        <varname>conninfo</varname> setting must be able to access this database and
-        the database objects contained within the extension.
-      </para>
-      <para>
-        The <literal>repmgr</literal> extension can only be installed by a superuser.
-        If the &repmgr; user is a superuser, &repmgr; will create the extension automatically.
-      </para>
-
-      <para>
-        Alternatively, the extension can be created manually by a superuser
-        (with &quot;<command>CREATE EXTENSION repmgr</command>&quot;) before executing
-        <link linkend="repmgr-primary-register">repmgr primary register</link>.
-      </para>
-    </sect3>
-
-
-    <sect3 id="configuration-permissions-functions" xreflabel="Function permissions for non-superusers">
-      <title>Function permissions</title>
-      <para>
-        If the &repmgr; database user is not a superuser, <literal>EXECUTE</literal> permission should be
-        granted on the following function:
-        <itemizedlist spacing="compact" mark="bullet">
-          <listitem>
-            <simpara>
-              <function>pg_wal_replay_resume()</function> (required by &repmgrd; during failover operations;
-              if permission is not granted, the failoved process may not function reliably if a node
-              has WAL replay paused)
-            </simpara>
-          </listitem>
-          <listitem>
-            <simpara>
-              <function>pg_promote()</function> (PostgreSQL 12 and later; if permission is not granted,
-              &repmgr; will fall back to <command>pg_ctl promote</command>)
-            </simpara>
-          </listitem>
-        </itemizedlist>
-      </para>
-      <para>
-        <literal>EXECUTE</literal> permission on functions can be granted with e.g.:
-        <command>GRANT EXECUTE ON FUNCTION pg_catalog.pg_wal_replay_resume() TO repmgr</command>.
-      </para>
-    </sect3>
-
-    <sect3 id="configuration-permissions-superuser-required" xreflabel="repmgr actions requiring a superuser">
-      <title>repmgr actions requiring a superuser</title>
-      <para>
-        In some circumstances, &repmgr; may need to perform an operation which cannot be delegated to a
-        non-superuser.
-        <itemizedlist spacing="compact" mark="bullet">
-          <listitem>
-            <simpara>
-              The <command>CHECKPOINT</command> command is executed by
-              <link linkend="repmgr-standby-switchover">repmgr standby switchover</link>. This can only
-              be executed by a superuser; if the &repmgr; user is not a superuser,
-              the <option>-S</option>/<option>--superuser</option> should be used.
-              From PostgreSQL 15 the <varname>pg_checkpoint</varname> predefined role removes the need of
-              superuser permissions to perform <command>CHECKPOINT</command> command.
-            </simpara>
-            <simpara>
-              If &repmgr; is not able to execute <command>CHECKPOINT</command>,
-              there is a risk that the demotion candidate may not  be able to shut down as smoothly as might otherwise
-              have been the case.
-            </simpara>
-          </listitem>
-          <listitem>
-            <simpara>
-              The <command>ALTER SYSTEM</command> is executed by &repmgrd; if
-              <varname>standby_disconnect_on_failover</varname> is set to <literal>true</literal> in
-              <filename>repmgr.conf</filename>. Until PostgreSQL 14 <command>ALTER SYSTEM</command> can only be executed by
-              a superuser; if the &repmgr; user is not a superuser, this functionality will not be available.
-              From PostgreSQL 15 a specific ALTER SYSTEM privilege can be granted with e.g.
-              <command>GRANT ALTER SYSTEM ON PARAMETER wal_retrieve_retry_interval TO repmgr</command>.
-            </simpara>
-          </listitem>
-        </itemizedlist>
-      </para>
-    </sect3>
-
-    <sect3 id="configuration-permissions-superuser-option" xreflabel="repmgr commands with --superuser option">
-      <title>repmgr commands with --superuser option</title>
-      <para>
-        The following repmgr commands provide the <option>-S</option>/<option>--superuser</option> option:
-        <itemizedlist spacing="compact" mark="bullet">
-          <listitem>
-            <simpara><link linkend="repmgr-standby-clone">repmgr standby clone</link> (to be able to copy configuration files outside of the data directory if <option>--copy-external-config-files</option> provided)</simpara>
-          </listitem>
-          <listitem>
-            <simpara><link linkend="repmgr-standby-switchover">repmgr standby switchover</link> (to execute <command>CHECKPOINT</command>)</simpara>
-          </listitem>
-          <listitem>
-            <simpara><link linkend="repmgr-node-check">repmgr node check</link> (to execute <command>repmgr node check --data-directory-config</command>; note this is also called by <link linkend="repmgr-standby-switchover">repmgr standby switchover</link>)</simpara>
-          </listitem>
-          <listitem>
-            <simpara><link linkend="repmgr-node-service">repmgr node service</link> (to execute <command>CHECKPOINT</command> via the <option>--checkpoint</option>; note this is also called by <link linkend="repmgr-standby-switchover">repmgr standby switchover</link>)</simpara>
-          </listitem>
-        </itemizedlist>
-      </para>
-    </sect3>
-
-  </sect2>
-</sect1>

doc/configuration.xml

@@ -1,335 +0,0 @@
-<chapter id="configuration" xreflabel="Configuration">
-  <title>repmgr configuration</title>
-
-  <sect1 id="configuration-prerequisites" xreflabel="Prerequisites for configuration">
-    <title>Prerequisites for configuration</title>
-
-    <indexterm>
-      <primary>configuration</primary>
-      <secondary>prerequisites</secondary>
-    </indexterm>
-
-    <indexterm>
-      <primary>configuration</primary>
-      <secondary>ssh</secondary>
-    </indexterm>
-
-    <para>
-     Following software must be installed on both servers:
-     <itemizedlist spacing="compact" mark="bullet">
-      <listitem>
-       <simpara><application>PostgreSQL</application></simpara>
-      </listitem>
-      <listitem>
-       <simpara>
-        <application>repmgr</application>
-       </simpara>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-      At network level, connections between the PostgreSQL port (default: <literal>5432</literal>)
-      must be possible between all nodes.
-    </para>
-
-    <para>
-      Passwordless <command>SSH</command> connectivity between all servers in the replication cluster
-      is not required, but is necessary in the following cases:
-      <itemizedlist>
-        <listitem>
-          <simpara>if you need &repmgr; to copy configuration files from outside the PostgreSQL
-            data directory (as is the case with e.g. <link linkend="packages-debian-ubuntu">Debian packages</link>);
-            in this case <command>rsync</command> must also be installed on all servers.
-          </simpara>
-        </listitem>
-        <listitem>
-          <simpara>to perform <link linkend="performing-switchover">switchover operations</link></simpara>
-        </listitem>
-        <listitem>
-          <simpara>
-            when executing <command><link linkend="repmgr-cluster-matrix">repmgr cluster matrix</link></command>
-            and <command><link linkend="repmgr-cluster-crosscheck">repmgr cluster crosscheck</link></command>
-          </simpara>
-        </listitem>
-      </itemizedlist>
-    </para>
-
-    <tip>
-      <simpara>
-        Consider setting <varname>ConnectTimeout</varname> to a low value in your SSH configuration.
-        This will make it faster to detect any SSH connection errors.
-      </simpara>
-    </tip>
-
-  <sect2 id="configuration-postgresql" xreflabel="PostgreSQL configuration">
-      <title>PostgreSQL configuration for &repmgr;</title>
-
-    <indexterm>
-      <primary>configuration</primary>
-      <secondary>PostgreSQL</secondary>
-    </indexterm>
-
-    <indexterm>
-      <primary>PostgreSQL configuration</primary>
-    </indexterm>
-
-    <para>
-      The following PostgreSQL configuration parameters may need to be changed in order
-      for &repmgr; (and replication itself) to function correctly.
-    </para>
-    <variablelist>
-
-
-      <varlistentry>
-
-        <term><option>hot_standby</option></term>
-        <listitem>
-
-          <indexterm>
-            <primary>hot_standby</primary>
-            <secondary>PostgreSQL configuration</secondary>
-          </indexterm>
-
-          <para>
-            <option>hot_standby</option> must always be set to <literal>on</literal>, as &repmgr; needs
-            to be able to connect to each server it manages.
-          </para>
-          <para>
-            Note that <option>hot_standby</option> defaults to <literal>on</literal> from PostgreSQL 10
-            and later; in PostgreSQL 9.6 and earlier, the default was <literal>off</literal>.
-          </para>
-          <para>
-            PostgreSQL documentation: <ulink url="https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-HOT-STANDBY">hot_standby</ulink>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-
-        <term><option>wal_level</option></term>
-
-        <listitem>
-
-          <indexterm>
-            <primary>wal_level</primary>
-            <secondary>PostgreSQL configuration</secondary>
-          </indexterm>
-
-          <para>
-            <option>wal_level</option> must be one of <option>replica</option> or <option>logical</option>
-            (PostgreSQL 9.5 and earlier: one of <option>hot_standby</option> or <option>logical</option>).
-          </para>
-          <para>
-            PostgreSQL documentation: <ulink url="https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-WAL-LEVEL">wal_level</ulink>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-
-        <term><option>max_wal_senders</option></term>
-
-        <listitem>
-
-          <indexterm>
-            <primary>max_wal_senders</primary>
-            <secondary>PostgreSQL configuration</secondary>
-          </indexterm>
-
-          <para>
-            <option>max_wal_senders</option> must be set to a value of <literal>2</literal> or greater.
-            In general you will need one WAL sender for each standby which will attach to the PostgreSQL
-            instance; additionally &repmgr; will require two free WAL senders in order to clone further
-            standbys.
-          </para>
-          <para>
-            <option>max_wal_senders</option> should be set to an appropriate value on all PostgreSQL
-            instances in the replication cluster which may potentially become a primary server or
-            (in cascading replication) the upstream server of a standby.
-          </para>
-         <para>
-            PostgreSQL documentation: <ulink url="https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-WAL-SENDERS">max_wal_senders</ulink>.
-          </para>
-          <note>
-            <para>
-              From <productname>PostgreSQL 12</productname>, <option>max_wal_senders</option>
-              <emphasis>must</emphasis> be set to the same or a higher value as the primary node
-              (at the time the node was cloned), otherwise the standby will refuse
-              to start (unless <option>hot_standby</option> is set to <literal>off</literal>, which
-              will prevent the node from accepting queries).
-            </para>
-          </note>
-
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-
-        <term><option>max_replication_slots</option></term>
-
-        <listitem>
-
-          <indexterm>
-            <primary>max_replication_slots</primary>
-            <secondary>PostgreSQL configuration</secondary>
-          </indexterm>
-
-          <para>
-            If you are intending to use replication slots, <option>max_replication_slots</option>
-            must be set to a non-zero value.
-          </para>
-          <para>
-            <option>max_replication_slots</option> should be set to an appropriate value on all PostgreSQL
-            instances in the replication cluster which may potentially become a primary server or
-            (in cascading replication) the upstream server of a standby.
-          </para>
-          <para>
-            PostgreSQL documentation: <ulink url="https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-REPLICATION-SLOTS">max_replication_slots</ulink>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-
-        <term><option>wal_log_hints</option></term>
-        <listitem>
-          <indexterm>
-            <primary>wal_log_hints</primary>
-            <secondary>PostgreSQL configuration</secondary>
-          </indexterm>
-
-
-          <para>If you are intending to use <application>pg_rewind</application>,
-            and the cluster was not initialised using data checksums, you may want to consider enabling
-            <option>wal_log_hints</option>.
-          </para>
-          <para>
-            For more details see <xref linkend="repmgr-node-rejoin-pg-rewind"/>.
-          </para>
-          <para>
-            PostgreSQL documentation: <ulink url="https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-WAL-LOG-HINTS">wal_log_hints</ulink>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-
-        <term><option>archive_mode</option></term>
-
-        <listitem>
-
-          <indexterm>
-            <primary>archive_mode</primary>
-            <secondary>PostgreSQL configuration</secondary>
-          </indexterm>
-
-          <para>
-            We suggest setting <option>archive_mode</option> to <literal>on</literal> (and
-            <option>archive_command</option> to <literal>/bin/true</literal>; see below)
-            even if you are currently not planning to use WAL file archiving.
-          </para>
-          <para>
-            This will make it simpler to set up WAL file archiving if it is ever required,
-            as changes to <option>archive_mode</option> require a full PostgreSQL server
-            restart, while <option>archive_command</option> changes can be applied via a normal
-            configuration reload.
-          </para>
-          <para>
-            However, &repmgr; itself does not require WAL file archiving.
-          </para>
-          <para>
-            PostgreSQL documentation: <ulink url="https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-ARCHIVE-MODE">archive_mode</ulink>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-
-        <term><option>archive_command</option></term>
-
-        <listitem>
-
-          <indexterm>
-            <primary>archive_command</primary>
-            <secondary>PostgreSQL configuration</secondary>
-          </indexterm>
-
-          <para>
-            If you have set  <option>archive_mode</option> to <literal>on</literal> but are not currently planning
-            to use WAL file archiving, set <option>archive_command</option> to a command which does nothing but returns
-            <literal>true</literal>, such as <command>/bin/true</command>. See above for details.
-          </para>
-          <para>
-            PostgreSQL documentation: <ulink url="https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-ARCHIVE-COMMAND">archive_command</ulink>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-
-        <term><option>wal_keep_segments</option> / <option>wal_keep_size</option></term>
-
-        <listitem>
-
-          <indexterm>
-            <primary>wal_keep_segments</primary>
-            <secondary>PostgreSQL configuration</secondary>
-          </indexterm>
-
-
-          <indexterm>
-            <primary>wal_keep_size</primary>
-            <secondary>PostgreSQL configuration</secondary>
-          </indexterm>
-
-          <para>
-            Normally there is no need to set <option>wal_keep_segments</option>
-            (PostgreSQL 13 and later: <varname>wal_keep_size</varname>; default: <literal>0</literal>),
-            as it is <emphasis>not</emphasis> a reliable way of ensuring that all required WAL
-            segments are available to standbys. Replication slots and/or an archiving solution
-            such as Barman are recommended to ensure standbys have a reliable
-            source of WAL segments at all times.
-          </para>
-          <para>
-            The only reason ever to set  <option>wal_keep_segments</option> / <option>wal_keep_size</option>
-            is you have you have configured <option>pg_basebackup_options</option>
-            in <filename>repmgr.conf</filename> to include the setting <literal>--wal-method=fetch</literal>
-            (PostgreSQL 9.6 and earlier: <literal>--xlog-method=fetch</literal>)
-            <emphasis>and</emphasis> you have <emphasis>not</emphasis> set <option>restore_command</option>
-            in <filename>repmgr.conf</filename> to fetch WAL files from a reliable source such as Barman,
-            in which case you'll need to set <option>wal_keep_segments</option>
-            to a sufficiently high number to ensure that all WAL files required by the standby
-            are retained. However we do not recommend WAL retention in this way.
-          </para>
-          <para>
-            PostgreSQL documentation: <ulink url="https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-WAL-KEEP-SEGMENTS">wal_keep_segments</ulink>.
-            <!--
-             PostgreSQL documentation: <ulink url="https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-WAL-KEEP-SIZE">wal_keep_size</ulink>.
-              -->
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-    <para>
-      See also the <link linkend="quickstart-postgresql-configuration">PostgreSQL configuration</link> section in the
-      <link linkend="quickstart">Quick-start guide</link>.
-    </para>
-  </sect2>
-
-
-  </sect1>
-
-
-  &configuration-file;
-  &configuration-file-required-settings;
-  &configuration-file-optional-settings;
-  &configuration-file-log-settings;
-  &configuration-file-service-commands;
-  &configuration-permissions;
-  &configuration-password-management;
-
-</chapter>

doc/event-notifications.xml

@@ -1,282 +0,0 @@
-<chapter id="event-notifications" xreflabel="event notifications">
- <title>Event Notifications</title>
-
- <indexterm>
-   <primary>event notifications</primary>
- </indexterm>
-
- <para>
-  Each time &repmgr; or &repmgrd; perform a significant event, a record
-  of that event is written into the <literal>repmgr.events</literal> table together with
-  a timestamp, an indication of failure or success, and further details
-  if appropriate. This is useful for gaining an overview of events
-  affecting the replication cluster. However note that this table has
-  advisory character and should be used in combination with the &repmgr;
-  and PostgreSQL logs to obtain details of any events.
- </para>
- <para>
-  Example output after a primary was registered and a standby cloned
-  and registered:
-  <programlisting>
-    repmgr=# SELECT * from repmgr.events ;
-     node_id |      event       | successful |        event_timestamp        |                                       details
-    ---------+------------------+------------+-------------------------------+-------------------------------------------------------------------------------------
-           1 | primary_register | t          | 2016-01-08 15:04:39.781733+09 |
-           2 | standby_clone    | t          | 2016-01-08 15:04:49.530001+09 | Cloned from host 'repmgr_node1', port 5432; backup method: pg_basebackup; --force: N
-           2 | standby_register | t          | 2016-01-08 15:04:50.621292+09 |
-    (3 rows)</programlisting>
- </para>
- <para>
-  Alternatively, use <xref linkend="repmgr-cluster-event"/> to output a
-  formatted list of events.
- </para>
- <para>
-  Additionally, event notifications can be passed to a user-defined program
-  or script which can take further action, e.g. send email notifications.
-  This is done by setting the <literal>event_notification_command</literal> parameter in
-  <filename>repmgr.conf</filename>.
- </para>
- <para>
-  The following format placeholders are provided for all event notifications:
- </para>
-
- <variablelist>
-  <varlistentry>
-   <term><option>%n</option></term>
-   <listitem>
-    <para>
-      node ID
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><option>%e</option></term>
-   <listitem>
-    <para>
-     event type
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><option>%s</option></term>
-   <listitem>
-    <para>
-     success (1) or failure (0)
-    </para>
-   </listitem>
-  </varlistentry>
-  <varlistentry>
-   <term><option>%t</option></term>
-   <listitem>
-    <para>
-     timestamp
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><option>%d</option></term>
-   <listitem>
-    <para>
-     details
-    </para>
-   </listitem>
-  </varlistentry>
- </variablelist>
-
- <para>
-  The values provided for <literal>%t</literal> and <literal>%d</literal>
-  may contain spaces, so should be quoted in the provided command
-  configuration, e.g.:
-  <programlisting>
-    event_notification_command='/path/to/some/script %n %e %s "%t" "%d"'</programlisting>
- </para>
-
- <para>
-   The following parameters are provided for a subset of event notifications; their meaning may
-   change according to context:
- </para>
-
- <variablelist>
-  <varlistentry>
-   <term><option>%p</option></term>
-   <listitem>
-    <para>
-     node ID of the current primary (<xref linkend="repmgr-standby-register"/> and <xref linkend="repmgr-standby-follow"/>)
-    </para>
-    <para>
-     node ID of the demoted primary (<xref linkend="repmgr-standby-switchover"/> only)
-    </para>
-    <para>
-     node ID of the former primary (<literal>repmgrd_failover_promote</literal> only)
-    </para>
-   </listitem>
-  </varlistentry>
-  <varlistentry>
-   <term><option>%c</option></term>
-   <listitem>
-    <para>
-     <literal>conninfo</literal> string of the primary node
-     (<xref linkend="repmgr-standby-register"/> and <xref linkend="repmgr-standby-follow"/>)
-    </para>
-   </listitem>
-  </varlistentry>
-
-  <varlistentry>
-   <term><option>%a</option></term>
-   <listitem>
-    <para>
-     name of the current primary node (<xref linkend="repmgr-standby-register"/> and <xref linkend="repmgr-standby-follow"/>)
-    </para>
-   </listitem>
-  </varlistentry>
-
- </variablelist>
-
- <para>
-  The values provided for <literal>%c</literal> and <literal>%a</literal>
-  may contain spaces, so should always be quoted.
- </para>
-
- <para>
-  By default, all notification types will be passed to the designated script;
-  the notification types can be filtered to explicitly named ones using the
-  <varname>event_notifications</varname> parameter, e.g.:
-    <programlisting>
-    event_notifications='primary_register,standby_register,witness_register'</programlisting>
-
- </para>
-
- <para>
-   Events generated by the &repmgr; command:
-
-  <itemizedlist spacing="compact" mark="bullet">
-
-   <listitem>
-     <simpara><literal><link linkend="repmgr-primary-register-events">cluster_created</link></literal></simpara>
-   </listitem>
-   <listitem>
-     <simpara><literal><link linkend="repmgr-primary-register-events">primary_register</link></literal></simpara>
-   </listitem>
-   <listitem>
-     <simpara><literal><link linkend="repmgr-primary-unregister-events">primary_unregister</link></literal></simpara>
-   </listitem>
-
-   <listitem>
-    <simpara><literal><link linkend="repmgr-standby-clone-events">standby_clone</link></literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal><link linkend="repmgr-standby-register-events">standby_register</link></literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal><link linkend="repmgr-standby-register-events">standby_register_sync</link></literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal><link linkend="repmgr-standby-unregister-events">standby_unregister</link></literal></simpara>
-   </listitem>
-
-   <listitem>
-    <simpara><literal><link linkend="repmgr-standby-promote-events">standby_promote</link></literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal><link linkend="repmgr-standby-follow-events">standby_follow</link></literal></simpara>
-   </listitem>
-   <listitem>
-     <simpara><literal><link linkend="repmgr-standby-switchover-events">standby_switchover</link></literal></simpara>
-   </listitem>
-
-   <listitem>
-     <simpara><literal><link linkend="repmgr-witness-register-events">witness_register</link></literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal><link linkend="repmgr-witness-unregister-events">witness_unregister</link></literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal><link linkend="repmgr-node-rejoin-events">node_rejoin</link></literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal><link linkend="repmgr-cluster-cleanup-events">cluster_cleanup</link></literal></simpara>
-   </listitem>
-
-  </itemizedlist>
- </para>
-
- <para>
-   Events generated by &repmgrd; (streaming replication mode):
-
-   <itemizedlist spacing="compact" mark="bullet">
-   <listitem>
-    <simpara><literal>repmgrd_start</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_shutdown</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_reload</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_failover_promote</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_failover_follow</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_failover_aborted</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_standby_reconnect</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_promote_error</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_local_disconnect</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_local_reconnect</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_upstream_disconnect</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>repmgrd_upstream_reconnect</literal></simpara>
-   </listitem>
-
-   <listitem>
-    <simpara><literal>standby_disconnect_manual</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>standby_failure</literal></simpara>
-   </listitem>
-   <listitem>
-    <simpara><literal>standby_recovery</literal></simpara>
-   </listitem>
-
-   <listitem>
-     <simpara><literal><link linkend="repmgrd-primary-child-disconnection-events">child_node_disconnect</link></literal></simpara>
-   </listitem>
-   <listitem>
-     <simpara><literal><link linkend="repmgrd-primary-child-disconnection-events">child_node_reconnect</link></literal></simpara>
-   </listitem>
-   <listitem>
-     <simpara><literal><link linkend="repmgrd-primary-child-disconnection-events">child_node_new_connect</link></literal></simpara>
-   </listitem>
-   <listitem>
-     <simpara><literal><link linkend="repmgrd-primary-child-disconnection-events">child_nodes_disconnect_command</link></literal></simpara>
-   </listitem>
-
-   </itemizedlist>
- </para>
-
- <para>
-  Note that under some circumstances (e.g. when no replication cluster primary
-  could be located), it will not be possible to write an entry into the
-  <literal>repmgr.events</literal>
-  table, in which case executing a script via <varname>event_notification_command</varname>
-  can serve as a fallback by generating some form of notification.
- </para>
-
-
-</chapter>

doc/filelist.xml

@@ -1,71 +0,0 @@
-<!-- doc/filelist.xml -->
-
-<!ENTITY legal      SYSTEM "legal.xml">
-
-<!ENTITY bookindex  SYSTEM "bookindex.xml">
-
-
-<!--
- Include external documentation sections
- -->
-
-<!ENTITY overview      SYSTEM "overview.xml">
-<!ENTITY install SYSTEM "install.xml">
-<!ENTITY install-requirements      SYSTEM "install-requirements.xml">
-<!ENTITY install-packages      SYSTEM "install-packages.xml">
-<!ENTITY install-source      SYSTEM "install-source.xml">
-<!ENTITY quickstart      SYSTEM "quickstart.xml">
-<!ENTITY configuration      SYSTEM "configuration.xml">
-<!ENTITY configuration-file      SYSTEM "configuration-file.xml">
-<!ENTITY configuration-file-required-settings      SYSTEM "configuration-file-required-settings.xml">
-<!ENTITY configuration-file-optional-settings      SYSTEM "configuration-file-optional-settings.xml">
-<!ENTITY configuration-file-log-settings      SYSTEM "configuration-file-log-settings.xml">
-<!ENTITY configuration-file-service-commands   SYSTEM "configuration-file-service-commands.xml">
-<!ENTITY configuration-permissions   SYSTEM "configuration-permissions.xml">
-<!ENTITY configuration-password-management   SYSTEM "configuration-password-management.xml">
-<!ENTITY cloning-standbys  SYSTEM "cloning-standbys.xml">
-<!ENTITY promoting-standby  SYSTEM "promoting-standby.xml">
-<!ENTITY follow-new-primary  SYSTEM "follow-new-primary.xml">
-<!ENTITY switchover  SYSTEM "switchover.xml">
-
-<!ENTITY event-notifications  SYSTEM "event-notifications.xml">
-<!ENTITY upgrading-repmgr  SYSTEM "upgrading-repmgr.xml">
-
-<!ENTITY repmgrd-overview SYSTEM "repmgrd-overview.xml">
-<!ENTITY repmgrd-automatic-failover SYSTEM "repmgrd-automatic-failover.xml">
-<!ENTITY repmgrd-configuration SYSTEM "repmgrd-configuration.xml">
-<!ENTITY repmgrd-operation SYSTEM "repmgrd-operation.xml">
-
-<!ENTITY repmgr-primary-register SYSTEM "repmgr-primary-register.xml">
-<!ENTITY repmgr-primary-unregister SYSTEM "repmgr-primary-unregister.xml">
-<!ENTITY repmgr-standby-clone SYSTEM "repmgr-standby-clone.xml">
-<!ENTITY repmgr-standby-register SYSTEM "repmgr-standby-register.xml">
-<!ENTITY repmgr-standby-unregister SYSTEM "repmgr-standby-unregister.xml">
-<!ENTITY repmgr-standby-promote SYSTEM "repmgr-standby-promote.xml">
-<!ENTITY repmgr-standby-follow SYSTEM "repmgr-standby-follow.xml">
-<!ENTITY repmgr-standby-switchover SYSTEM "repmgr-standby-switchover.xml">
-<!ENTITY repmgr-witness-register SYSTEM "repmgr-witness-register.xml">
-<!ENTITY repmgr-witness-unregister SYSTEM "repmgr-witness-unregister.xml">
-<!ENTITY repmgr-node-status SYSTEM "repmgr-node-status.xml">
-<!ENTITY repmgr-node-check SYSTEM "repmgr-node-check.xml">
-<!ENTITY repmgr-node-rejoin SYSTEM "repmgr-node-rejoin.xml">
-<!ENTITY repmgr-node-service SYSTEM "repmgr-node-service.xml">
-<!ENTITY repmgr-cluster-show SYSTEM "repmgr-cluster-show.xml">
-<!ENTITY repmgr-cluster-matrix SYSTEM "repmgr-cluster-matrix.xml">
-<!ENTITY repmgr-cluster-crosscheck SYSTEM "repmgr-cluster-crosscheck.xml">
-<!ENTITY repmgr-cluster-event SYSTEM "repmgr-cluster-event.xml">
-<!ENTITY repmgr-cluster-cleanup SYSTEM "repmgr-cluster-cleanup.xml">
-<!ENTITY repmgr-service-status SYSTEM "repmgr-service-status.xml">
-<!ENTITY repmgr-service-pause SYSTEM "repmgr-service-pause.xml">
-<!ENTITY repmgr-service-unpause SYSTEM "repmgr-service-unpause.xml">
-<!ENTITY repmgr-daemon-start SYSTEM "repmgr-daemon-start.xml">
-<!ENTITY repmgr-daemon-stop SYSTEM "repmgr-daemon-stop.xml">
-
-<!ENTITY appendix-release-notes  SYSTEM "appendix-release-notes.xml">
-<!ENTITY appendix-faq      SYSTEM "appendix-faq.xml">
-<!ENTITY appendix-signatures      SYSTEM "appendix-signatures.xml">
-<!ENTITY appendix-packages      SYSTEM "appendix-packages.xml">
-<!ENTITY appendix-support SYSTEM "appendix-support.xml">
-
-<!ENTITY bookindex  SYSTEM "bookindex.xml">
-

doc/follow-new-primary.xml

@@ -1,49 +0,0 @@
-<chapter id="follow-new-primary">
- <title>Following a new primary</title>
-
- <indexterm>
-  <primary>Following a new primary</primary>
-  <seealso>repmgr standby follow</seealso>
- </indexterm>
-
- <para>
-   Following the failure or removal of the replication cluster's existing primary
-   server, <xref linkend="repmgr-standby-follow"/> can be used to make &quot;orphaned&quot; standbys
-   follow the new primary and catch up to its current state.
- </para>
- <para>
-  To demonstrate this, assuming a replication cluster in the same state as the
-  end of the preceding section (<xref linkend="promoting-standby"/>),
-  execute this:
-  <programlisting>
-    $ repmgr -f /etc/repmgr.conf standby follow
-    INFO: changing node 3's primary to node 2
-    NOTICE: restarting server using "pg_ctl -l /var/log/postgresql/startup.log -w -D '/var/lib/postgresql/data' restart"
-    waiting for server to shut down......... done
-    server stopped
-    waiting for server to start.... done
-    server started
-    NOTICE: STANDBY FOLLOW successful
-    DETAIL: node 3 is now attached to node 2
-  </programlisting>
- </para>
- <para>
-   The standby is now replicating from the new primary and
-   <command><link linkend="repmgr-cluster-show">repmgr cluster show</link></command>
-   output reflects this:
-   <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster show
-     ID | Name  | Role    | Status    | Upstream | Location | Connection string
-    ----+-------+---------+-----------+----------+----------+--------------------------------------
-     1  | node1 | primary | - failed  |          | default  | host=node1 dbname=repmgr user=repmgr
-     2  | node2 | primary | * running |          | default  | host=node2 dbname=repmgr user=repmgr
-     3  | node3 | standby |   running | node2    | default  | host=node3 dbname=repmgr user=repmgr</programlisting>
- </para>
- <para>
-  Note that with cascading replication, <command>repmgr standby follow</command> can also be
-  used to detach a standby from its current upstream server and follow the
-  primary. However it's currently not possible to have it follow another standby;
-  we hope to improve this in a future release.
- </para>
-
-</chapter>

doc/install-packages.xml

@@ -1,285 +0,0 @@
-<sect1 id="installation-packages" xreflabel="Installing from packages">
- <title>Installing &repmgr; from packages</title>
-
-  <indexterm>
-   <primary>installation</primary>
-   <secondary>from packages</secondary>
-  </indexterm>
-
- <para>
-  We recommend installing &repmgr; using the available packages for your
-  system.
- </para>
-
- <sect2 id="installation-packages-redhat" xreflabel="Installing from packages on RHEL, CentOS and Fedora">
-
-  <title>RedHat/CentOS/Fedora</title>
-
-  <indexterm>
-   <primary>installation</primary>
-   <secondary>on Red Hat/CentOS/Fedora etc.</secondary>
-  </indexterm>
-
-  <para>
-	&repmgr; RPM packages for RedHat/CentOS variants and Fedora are available from the
-	<ulink url="https://www.enterprisedb.com">EDB</ulink>
-	<ulink url="https://dl.enterprisedb.com/">public repository</ulink>; see following
-	section for details.
-  </para>
-  <note>
-    <para>
-      Currently the <ulink url="https://www.enterprisedb.com">EDB</ulink>
-	  <ulink url="https://dl.enterprisedb.com/">public repository</ulink> provides
-      support for RedHat/CentOS versions 6,7 and 8.
-    </para>
-  </note>
-  <para>
-   RPM packages for &repmgr; are also available via Yum through
-   the PostgreSQL Global Development Group (PGDG) RPM repository
-   (<ulink url="https://yum.postgresql.org/">https://yum.postgresql.org/</ulink>).
-   Follow the instructions for your distribution (RedHat, CentOS,
-   Fedora, etc.) and architecture as detailed there. Note that it can take some days
-   for new &repmgr; packages to become available via the this repository.
-  </para>
-  <note>
-    <para>
-      &repmgr; RPM packages are designed to be compatible with the community-provided PostgreSQL packages
-      and EDB's PostgreSQL Extended Server (formerly 2ndQPostgres).
-      They may not work with vendor-specific packages such as those provided by RedHat for RHEL
-      customers, as the PostgreSQL filesystem layout may be different to the community RPMs.
-      Please contact your support vendor for assistance.
-    </para>
-    <para>
-      See also <link linkend="appendix-faq">FAQ</link> entry
-      <xref linkend="faq-third-party-packages"/>.
-    </para>
-  </note>
-
-  <para>
-    For more information on the package contents, including details of installation
-    paths and relevant <link linkend="configuration-file-service-commands">service commands</link>,
-    see the appendix section <xref linkend="packages-centos"/>.
-  </para>
-
-
-  <sect3 id="installation-packages-redhat-2ndq">
-    <title>EDB public RPM yum repository</title>
-
-    <para>
-      <ulink url="https://www.enterprisedb.com/">EDB</ulink> provides a dedicated <literal>yum</literal>
-      <ulink url="https://dl.enterprisedb.com/">public repository</ulink> for EDB software,
-      including &repmgr;. We recommend using this for all future &repmgr; releases.
-    </para>
-    <para>
-      General instructions for using this repository can be found on its
-      <ulink url="https://dl.enterprisedb.com/">homepage</ulink>. Specific instructions
-      for installing &repmgr; follow below.
-    </para>
-    <para>
-      <emphasis>Installation</emphasis>
-
-      <itemizedlist>
-	<listitem>
-	  <para>
-	    Locate the repository RPM for your PostgreSQL version from the list at:
-	    <ulink url="https://dl.enterprisedb.com/">https://dl.enterprisedb.com/</ulink>
-	  </para>
-	</listitem>
-
-    <listitem>
-      <para>
-        Install the repository definition for your distribution and PostgreSQL version
-	    (this enables the EDB repository as a source of &repmgr; packages).
-	  </para>
-	  <para>
-	    For example, for PostgreSQL 14 on Rocky Linux 8, execute:
-	    <programlisting>
-curl https://dl.enterprisedb.com/default/release/get/14/rpm | sudo bash</programlisting>
-	  </para>
-
-	  <para>
-	    Verify that the repository is installed with:
-	    <programlisting>
-sudo dnf repolist</programlisting>
-	    The output should contain two entries like this:
-	    <programlisting>
-2ndquadrant-dl-default-release-pg14                  2ndQuadrant packages (PG14) for 8 - x86_64
-2ndquadrant-dl-default-release-pg14-debug            2ndQuadrant packages (PG14) for 8 - x86_64 - Debug</programlisting>
-	  </para>
-	</listitem>
-
-        <listitem>
-          <para>
-            Install the &repmgr; version appropriate for your PostgreSQL version (e.g. <literal>repmgr14</literal>):
-            <programlisting>
-sudo dnf install repmgr14</programlisting>
-          </para>
-          <tip>
-            <para>
-              To determine the names of available packages, execute:
-              <programlisting>
-dnf search repmgr</programlisting>
-            </para>
-            <para>
-              In CentOS 7 and earlier, use <literal>yum</literal> instead of <literal>dnf</literal>.
-            </para>
-          </tip>
-
-        </listitem>
-      </itemizedlist>
-    </para>
-
-    <para>
-      <emphasis>Compatibility with PGDG Repositories</emphasis>
-    </para>
-    <para>
-      The EDB &repmgr; yum repository packages use the same definitions and file system layout as the
-      main PGDG repository.
-    </para>
-    <para>
-      Normally <application>yum</application> will prioritize the repository with the most recent &repmgr; version.
-      Once the PGDG repository has been updated, it doesn't matter which repository
-      the packages are installed from.
-    </para>
-    <para>
-      To ensure the EDB repository is always prioritised, set the <literal>priority</literal> option
-      in the repository configuration file (e.g. <filename>/etc/yum.repos.d/2ndquadrant-dl-default-release-pg14.repo</filename>
-      accordingly.
-    </para>
-    <note>
-      <para>
-        With CentOS 7 and earlier, the package <literal>yum-plugin-priorities</literal> must be installed
-        to be able to set the repository priority.
-      </para>
-    </note>
-
-    <para>
-      <emphasis>Installing a specific package version</emphasis>
-    </para>
-    <para>
-      To install a specific package version, execute <command>dnf --showduplicates list</command>
-      for the package in question:
-      <programlisting>
-[root@localhost ~]# dnf --showduplicates list repmgr10
-Last metadata expiration check: 0:09:15 ago on Fri 11 Mar 2022 01:09:19 AM UTC.
-Installed Packages
-repmgr10.x86_64                            5.3.1-1.el8                              @2ndquadrant-dl-default-release-pg10
-Available Packages
-repmgr10.x86_64                            5.0.0-1.rhel8                            pgdg10
-repmgr10.x86_64                            5.1.0-1.el8                              2ndquadrant-dl-default-release-pg10
-repmgr10.x86_64                            5.1.0-1.rhel8                            pgdg10
-repmgr10.x86_64                            5.1.0-2.el8                              2ndquadrant-dl-default-release-pg10
-repmgr10.x86_64                            5.2.0-1.el8                              2ndquadrant-dl-default-release-pg10
-repmgr10.x86_64                            5.2.0-1.rhel8                            pgdg10
-repmgr10.x86_64                            5.2.1-1.el8                              2ndquadrant-dl-default-release-pg10
-repmgr10.x86_64                            5.3.0-1.el8                              2ndquadrant-dl-default-release-pg10
-repmgr10.x86_64                            5.3.1-1.el8                              2ndquadrant-dl-default-release-pg10</programlisting>
-      then append the appropriate version number to the package name with a hyphen, e.g.:
-      <programlisting>
-[root@localhost ~]# dnf install repmgr10-5.3.0-1.el8</programlisting>
-    </para>
-    <para>
-      <emphasis>Installing old packages</emphasis>
-    </para>
-    <para>
-      See appendix <link linkend="packages-old-versions-rhel-centos">Installing old package versions</link>
-      for details on how to retrieve older package versions.
-    </para>
-  </sect3>
-
- </sect2>
-
- <sect2 id="installation-packages-debian" xreflabel="Installing from packages on Debian or Ubuntu">
-
-  <title>Debian/Ubuntu</title>
-
-  <indexterm>
-   <primary>installation</primary>
-   <secondary>on Debian/Ubuntu etc.</secondary>
-  </indexterm>
-
-  <para>.deb packages for &repmgr; are available from the
-  PostgreSQL Community APT repository (<ulink url="https://apt.postgresql.org/">https://apt.postgresql.org/</ulink>).
-  Instructions can be found in the APT section of the PostgreSQL Wiki
-  (<ulink url="https://wiki.postgresql.org/wiki/Apt">https://wiki.postgresql.org/wiki/Apt</ulink>).
-  </para>
-  <para>
-    For more information on the package contents, including details of installation
-    paths and relevant <link linkend="configuration-file-service-commands">service commands</link>,
-    see the appendix section <xref linkend="packages-debian-ubuntu"/>.
-  </para>
-
-  <sect3 id="installation-packages-debian-ubuntu-2ndq">
-    <title>EDB public apt repository for Debian/Ubuntu</title>
-
-    <para>
-      <ulink url="https://www.enterprisedb.com/">EDB</ulink> provides a
-      <ulink url="https://dl.enterprisedb.com/">public apt repository</ulink> for EDB software,
-      including &repmgr;.
-    </para>
-    <para>
-      General instructions for using this repository can be found on its
-      <ulink url="https://dl.enterprisedb.com/">homepage</ulink>. Specific instructions
-      for installing &repmgr; follow below.
-    </para>
-
-    <para>
-
-      <emphasis>Installation</emphasis>
-
-      <itemizedlist>
-
-	    <listitem>
-	      <para>
-            Install the repository definition for your distribution and PostgreSQL version
-	        (this enables the EDB repository as a source of &repmgr; packages) by executing:
-            <programlisting>
-              curl https://dl.enterprisedb.com/default/release/get/deb | sudo bash</programlisting>
-	      </para>
-          <note>
-            <para>
-              This will automatically install the following additional packages, if not already present:
-              <itemizedlist spacing="compact" mark="bullet">
-                <listitem>
-                  <simpara><literal>lsb-release</literal></simpara>
-                </listitem>
-                <listitem>
-                  <simpara><literal>apt-transport-https</literal></simpara>
-                </listitem>
-              </itemizedlist>
-            </para>
-          </note>
-        </listitem>
-
-	    <listitem>
-	      <para>
-            Install the &repmgr; version appropriate for your PostgreSQL version (e.g. <literal>repmgr11</literal>):
-            <programlisting>
-              sudo apt-get install postgresql-11-repmgr</programlisting>
-	      </para>
-          <note>
-            <para>
-              For packages for PostgreSQL 9.6 and earlier, the package name includes
-              a period between major and minor version numbers, e.g.
-              <literal>postgresql-9.6-repmgr</literal>.
-            </para>
-          </note>
-	    </listitem>
-
-      </itemizedlist>
-
-    </para>
-
-    <para>
-      <emphasis>Installing old packages</emphasis>
-    </para>
-    <para>
-      See appendix <link linkend="packages-old-versions-debian">Installing old package versions</link>
-      for details on how to retrieve older package versions.
-    </para>
-
-
-  </sect3>
- </sect2>
-
-</sect1>

doc/install-requirements.xml

@@ -1,346 +0,0 @@
-<sect1 id="install-requirements" xreflabel="installation requirements">
-
-  <title>Requirements for installing repmgr</title>
-
-  <indexterm>
-   <primary>installation</primary>
-   <secondary>requirements</secondary>
-  </indexterm>
-
-  <para>
-    repmgr is developed and tested on Linux and OS X, but should work on any
-    UNIX-like system supported by PostgreSQL itself. There is no support for
-    Microsoft Windows.
-  </para>
-
-  <para>
-   &repmgr; &repmgrversion; is compatible with all supported PostgreSQL versions from 13.x. See
-   section <link linkend="install-compatibility-matrix">&repmgr; compatibility matrix</link>
-   for an overview of version compatibility.
-  </para>
-
-  <note>
-   <simpara>
-    If upgrading from &repmgr; 3.x, please see the section <xref linkend="upgrading-from-repmgr-3"/>.
-   </simpara>
-  </note>
-
-  <para>
-   All servers in the replication cluster must be running the same major version of
-   PostgreSQL, and we recommend that they also run the same minor version.
-  </para>
-
-  <para>
-   &repmgr; must be installed on each server in the replication cluster.
-   If installing repmgr from packages, the package version must match the PostgreSQL
-   version. If installing from source, &repmgr; must be compiled against the same
-   major version.
-  </para>
-
-  <note>
-   <simpara>
-     The same &quot;major&quot; &repmgr; version (e.g. <literal>&repmgrversion;.x</literal>) <emphasis>must</emphasis>
-     be installed on all node in the replication cluster. We strongly recommend keeping all
-     nodes on the same (preferably latest) &quot;minor&quot; &repmgr; version to minimize the risk
-     of incompatibilities.
-   </simpara>
-   <simpara>
-     If different &quot;major&quot; &repmgr; versions (e.g. 5.2.x and &repmgrversion;)
-     are installed on different nodes, in the best case &repmgr; (in particular &repmgrd;)
-     will not run. In the worst case, you will end up with a broken cluster.
-   </simpara>
-  </note>
-
-  <para>
-   A dedicated system user for &repmgr; is <emphasis>not</emphasis> required; as many &repmgr; and
-   &repmgrd; actions require direct access to the PostgreSQL data directory,
-   these commands should be executed by the <literal>postgres</literal> user.
-  </para>
-
-  <para>
-    See also <link linkend="configuration-prerequisites">Prerequisites for configuration</link>
-    for information on networking requirements.
-  </para>
-
-  <tip>
-   <simpara>
-    We recommend using a session multiplexer utility such as <command>screen</command> or
-    <command>tmux</command> when performing long-running actions (such as cloning a database)
-    on a remote server - this will ensure the &repmgr; action won't be prematurely
-    terminated if your <command>ssh</command> session to the server is interrupted or closed.
-    </simpara>
-  </tip>
-
-  <sect2 id="install-compatibility-matrix">
-
-    <title>&repmgr; compatibility matrix</title>
-
-    <indexterm>
-      <primary>repmgr</primary>
-      <secondary>compatibility matrix</secondary>
-    </indexterm>
-
-    <indexterm>
-      <primary>compatibility matrix</primary>
-    </indexterm>
-
-    <para>
-      The following table provides an overview of which &repmgr; version supports
-      which PostgreSQL version.
-    </para>
-
-    <table id="repmgr-compatibility-matrix">
-      <title>&repmgr; compatibility matrix</title>
-
-      <tgroup cols="4">
-        <thead>
-          <row>
-            <entry>
-              &repmgr; version
-            </entry>
-            <entry>
-              Supported?
-            </entry>
-            <entry>
-              Latest release
-            </entry>
-            <entry>
-              Supported PostgreSQL versions
-            </entry>
-            <entry>
-              Notes
-            </entry>
-          </row>
-        </thead>
-
-        <tbody>
-          <row>
-            <entry>
-              &repmgr; 5.5
-            </entry>
-            <entry>
-              Yes
-            </entry>
-            <entry>
-              <link linkend="release-5.5.0">&repmgrversion;</link> (&releasedate;)
-            </entry>
-            <entry>
-              13, 14, 15, 16, 17
-            </entry>
-            <entry>
-              &nbsp;
-            </entry>
-          </row>
-
-          <row>
-            <entry>
-              &repmgr; 5.4.1
-            </entry>
-            <entry>
-              Yes
-            </entry>
-            <entry>
-              <link linkend="release-5.4.1">5.4.1</link> (2023-04-04)
-            </entry>
-            <entry>
-              10, 11, 12, 13, 14, 15
-            </entry>
-            <entry>
-              &nbsp;
-            </entry>
-          </row>
-
-          <row>
-            <entry>
-              &repmgr; 5.3.1
-            </entry>
-            <entry>
-              Yes
-            </entry>
-            <entry>
-              <link linkend="release-5.3.1">5.3.1</link> (2022-02-15)
-            </entry>
-            <entry>
-              9.4, 9.5, 9.6, 10, 11, 12, 13, 14, 15
-            </entry>
-            <entry>
-              PostgreSQL 15 supported from &repmgr; 5.3.3
-            </entry>
-          </row>
-
-          <row>
-            <entry>
-              &repmgr; 5.2
-            </entry>
-            <entry>
-              No
-            </entry>
-            <entry>
-              <link linkend="release-5.2.1">5.2.1</link> (2020-12-07)
-            </entry>
-            <entry>
-              9.4, 9.5, 9.6, 10, 11, 12, 13
-            </entry>
-            <entry>
-              &nbsp;
-            </entry>
-          </row>
-
-          <row>
-            <entry>
-              &repmgr; 5.1
-            </entry>
-            <entry>
-              No
-            </entry>
-            <entry>
-              <link linkend="release-5.1.0">5.1.0</link> (2020-04-13)
-            </entry>
-            <entry>
-              9.3, 9.4, 9.5, 9.6, 10, 11, 12
-            </entry>
-            <entry>
-              &nbsp;
-            </entry>
-          </row>
-
-          <row>
-            <entry>
-              &repmgr; 5.0
-            </entry>
-            <entry>
-              No
-            </entry>
-            <entry>
-              <link linkend="release-5.0">5.0</link> (2019-10-15)
-            </entry>
-            <entry>
-              9.3, 9.4, 9.5, 9.6, 10, 11, 12
-            </entry>
-            <entry>
-              &nbsp;
-            </entry>
-          </row>
-
-
-          <row>
-            <entry>
-              &repmgr; 4.x
-            </entry>
-            <entry>
-              No
-            </entry>
-            <entry>
-              <link linkend="release-4.4">4.4</link> (2019-06-27)
-            </entry>
-            <entry>
-              9.3, 9.4, 9.5, 9.6, 10, 11
-            </entry>
-            <entry>
-              &nbsp;
-            </entry>
-          </row>
-
-          <row>
-            <entry>
-              &repmgr; 3.x
-            </entry>
-            <entry>
-              No
-            </entry>
-            <entry>
-              <ulink url="https://repmgr.org/release-notes-3.3.2.html">3.3.2</ulink> (2017-05-30)
-            </entry>
-            <entry>
-              9.3, 9.4, 9.5, 9.6
-            </entry>
-            <entry>
-              &nbsp;
-            </entry>
-          </row>
-
-          <row>
-            <entry>
-              &repmgr; 2.x
-            </entry>
-            <entry>
-              No
-            </entry>
-            <entry>
-              <ulink url="https://repmgr.org/release-notes-2.0.3.html">2.0.3</ulink> (2015-04-16)
-            </entry>
-            <entry>
-              9.0, 9.1, 9.2, 9.3, 9.4
-            </entry>
-            <entry>
-              &nbsp;
-            </entry>
-          </row>
-        </tbody>
-
-      </tgroup>
-    </table>
-
-    <important>
-      <para>
-        The &repmgr; series older than 5.x are no longer maintained or supported.
-        We strongly recommend  upgrading to the latest &repmgr; version.
-      </para>
-      <para>
-        Following the release of &repmgr; 5.0, there will be no further releases of
-        the &repmgr; 4.x series or older. Note that &repmgr; 5.x is an incremental development
-        of the 4.x series and &repmgr; 4.x users should upgrade to this as soon as possible.
-      </para>
-    </important>
-
-  </sect2>
-
-  <sect2 id="install-postgresql-93-94">
-
-    <title>PostgreSQL 9.4 support</title>
-
-    <indexterm>
-      <primary>PostgreSQL 9.4</primary>
-      <secondary>repmgr support</secondary>
-    </indexterm>
-
-    <para>
-      Note that some &repmgr; functionality is not available in PostgreSQL 9.4:
-    </para>
-    <itemizedlist spacing="compact" mark="bullet">
-
-      <listitem>
-        <para>
-          In PostgreSQL 9.4, <command>pg_rewind</command> is not part of the core
-          distribution. <command>pg_rewind</command> will need to be compiled separately to be able
-          to use any &repmgr; functionality which takes advantage of it.
-        </para>
-      </listitem>
-    </itemizedlist>
-
-    <warning>
-      <para>
-        PostgreSQL 9.3 has reached the end of its community support period (final release was
-        <ulink url="https://www.postgresql.org/docs/9.3/release-9-3-25.html">9.3.25</ulink>
-        in November 2018) and will no longer be updated with security or bugfixes.
-      </para>
-      <para>
-        Beginning with &repmgr; 5.2, &repmgr; no longer supports PostgreSQL 9.3.
-      </para>
-      <para>
-        PostgreSQL 9.4 has reached the end of its community support period (final release was
-        <ulink url="https://www.postgresql.org/docs/9.4/release-9-4-26.html">9.4.26</ulink>
-        in February 2020) and will no longer be updated with security or bugfixes.
-      </para>
-      <para>
-        We recommend that users of these versions migrate to a supported PostgreSQL version
-        as soon as possible.
-      </para>
-      <para>
-        For further details, see the  <ulink url="https://www.postgresql.org/support/versioning/">PostgreSQL Versioning Policy</ulink>.
-      </para>
-    </warning>
-
-  </sect2>
-
- </sect1>

doc/install-source.xml

@@ -1,293 +0,0 @@
-<sect1 id="installation-source" xreflabel="Installing from source code">
-
- <title>Installing &repmgr; from source</title>
-
- <indexterm>
-  <primary>installation</primary>
-  <secondary>from source</secondary>
- </indexterm>
-
- <sect2 id="installation-source-prereqs">
-  <title>Prerequisites for installing from source</title>
-  <para>
-   To install &repmgr; the prerequisites for compiling
-   &postgres; must be installed. These are described in &postgres;'s
-   documentation
-   on <ulink url="https://www.postgresql.org/docs/current/install-requirements.html">build requirements</ulink>
-   and <ulink url="https://www.postgresql.org/docs/current/docguide-toolsets.html">build requirements for documentation</ulink>.
-  </para>
-
-  <para>
-   Most mainstream Linux distributions and other UNIX variants provide simple
-   ways to install the prerequisites from packages.
-   <itemizedlist spacing="compact" mark="bullet">
-    <listitem>
-     <para>
-      <literal>Debian</literal> and <literal>Ubuntu</literal>: First
-      add the <ulink url="https://apt.postgresql.org/">apt.postgresql.org</ulink>
-      repository to your <filename>sources.list</filename> if you
-      have not already done so, and ensure the source repository is enabled.
-     </para>
-     <tip>
-       <para>
-         If not configured, the source repository can be added by including
-         a <literal>deb-src</literal> line as a copy of the existing <literal>deb</literal>
-         line in the repository file, which is usually
-         <filename>/etc/apt/sources.list.d/pgdg.list</filename>, e.g.:
-         <programlisting>
-deb https://apt.postgresql.org/pub/repos/apt/ stretch-pgdg main
-deb-src https://apt.postgresql.org/pub/repos/apt/ stretch-pgdg main</programlisting>
-       </para>
-     </tip>
-     <para>
-      Then install the prerequisites for
-      building PostgreSQL with e.g.:
-      <programlisting>
-       sudo apt-get update
-       sudo apt-get build-dep postgresql-9.6</programlisting>
-      </para>
-
-     <important>
-       <simpara>
-         Select the appropriate PostgreSQL version for your target repmgr version.
-       </simpara>
-     </important>
-
-     <note>
-       <para>
-       If using <command>apt-get build-dep</command> is not possible, the
-       following packages may need to be installed manually:
-
-         <itemizedlist spacing="compact" mark="bullet">
-
-           <listitem>
-             <simpara><literal>flex</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libedit-dev</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libkrb5-dev</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libpam0g-dev</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libreadline-dev</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libselinux1-dev</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libssl-dev</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libxml2-dev</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libxslt1-dev</literal></simpara>
-           </listitem>
-         </itemizedlist>
-       </para>
-     </note>
-
-    </listitem>
-    <listitem>
-     <para>
-      <literal>RHEL or CentOS 6.x or 7.x</literal>: install the appropriate repository RPM
-      for your system from <ulink url="https://yum.postgresql.org/repopackages.php">
-      yum.postgresql.org</ulink>. Then install the prerequisites for building
-      PostgreSQL with:
-      <programlisting>
-       sudo yum check-update
-       sudo yum groupinstall "Development Tools"
-       sudo yum install yum-utils openjade docbook-dtds docbook-style-dsssl docbook-style-xsl
-       sudo yum-builddep postgresql96</programlisting>
-     </para>
-
-     <important>
-       <simpara>
-         Select the appropriate PostgreSQL version for your target repmgr version.
-       </simpara>
-     </important>
-     <note>
-       <para>
-         If using <command>yum-builddep</command> is not possible, the
-         following packages may need to be installed manually:
-
-         <itemizedlist spacing="compact" mark="bullet">
-
-           <listitem>
-             <simpara><literal>flex</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libselinux-devel</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libxml2-devel</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>libxslt-devel</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>openssl-devel</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>pam-devel</literal></simpara>
-           </listitem>
-           <listitem>
-             <simpara><literal>readline-devel</literal></simpara>
-           </listitem>
-
-         </itemizedlist>
-       </para>
-     </note>
-
-     <tip>
-       <para>
-         If building against PostgreSQL 11 or later configured with the <option>--with-llvm</option> option
-         (this is the case with the PGDG-provided packages) you'll also need to install the
-         <literal>llvm-toolset-7-clang</literal> package. This is available via the
-         <ulink url="https://wiki.centos.org/AdditionalResources/Repositories/SCL">Software Collections (SCL) Repository</ulink>.
-       </para>
-     </tip>
-
-    </listitem>
-   </itemizedlist>
-  </para>
-
- </sect2>
-
-
-<sect2 id="installation-get-source">
-  <title>Getting &repmgr; source code</title>
-
-  <para>
-   There are two ways to get the &repmgr; source code: with git, or by downloading tarballs of released versions.
-  </para>
-
-  <sect3>
-   <title>Using <application>git</application> to get the &repmgr; sources</title>
-
-   <para>
-    Use <application><ulink url="https://git-scm.com">git</ulink></application> if you expect
-    to update often, you want to keep track of development or if you want to contribute
-    changes to &repmgr;. There is no reason <emphasis>not</emphasis> to use <application>git</application>
-    if you're familiar with it.
-   </para>
-
-   <para>
-    The source for &repmgr; is maintained at
-    <ulink url="https://github.com/EnterpriseDB/repmgr">https://github.com/EnterpriseDB/repmgr</ulink>.
-   </para>
-
-   <para>
-    There are also tags for each <ulink url="https://github.com/EnterpriseDB/repmgr/releases">&repmgr; release</ulink>, e.g.
-    <literal><ulink url="https://github.com/EnterpriseDB/repmgr/releases/tag/v4.4.0">v4.4.0</ulink></literal>.
-   </para>
-
-   <para>
-    Clone the source code using <application>git</application>:
-    <programlisting>
-     git clone https://github.com/EnterpriseDB/repmgr</programlisting>
-   </para>
-
-   <para>
-    For more information on using <application>git</application> see
-    <ulink url="https://git-scm.com/">git-scm.com</ulink>.
-   </para>
-
-  </sect3>
-
-  <sect3>
-   <title>Downloading release source tarballs</title>
-
-   <para>
-    Official release source code is uploaded as tarballs to the
-    &repmgr; website along with a tarball checksum and a matching GnuPG
-    signature. See
-    <ulink url="http://repmgr.org/">http://repmgr.org/</ulink>
-    for the download information. See <xref linkend="appendix-signatures"/>
-    for information on verifying digital signatures.
-   </para>
-
-   <para>
-    You will need to download the repmgr source, e.g. <filename>repmgr-4.0.tar.gz</filename>.
-    You may optionally verify the package checksums from the
-    <literal>.md5</literal> files and/or verify the GnuPG signatures
-    per <xref linkend="appendix-signatures"/>.
-   </para>
-
-   <para>
-    After you unpack the source code archives using <command>tar xf</command>
-    the installation process is the same as if you were installing from a git
-    clone.
-   </para>
-
-  </sect3>
-
- </sect2>
-
- <sect2 id="installation-repmgr-source">
-  <title>Installation of &repmgr; from source</title>
-  <para>
-   To installing &repmgr; from source, simply execute:
-
-   <programlisting>
-    ./configure &amp;&amp; make install</programlisting>
-
-   Ensure <command>pg_config</command> for the target PostgreSQL version is in
-   <varname>$PATH</varname>.
-  </para>
- </sect2>
-
-
-
- <sect2 id="installation-build-repmgr-docs" xreflabel="Building repmgr documentation">
-   <title>Building &repmgr; documentation</title>
-   <para>
-    The &repmgr; documentation is (like the main PostgreSQL project)
-    written in DocBook XML format. To build it locally as HTML, you'll need to
-    install the required packages as described in the
-    <ulink url="https://www.postgresql.org/docs/current/docguide-toolsets.html">PostgreSQL documentation</ulink>.
-   </para>
-   <para>
-	 The minimum PostgreSQL version for building the &repmgr; documentation is
-	 PostgreSQL 9.5.
-   </para>
-
-   <note>
-     <simpara>
-       In &repmgr; 4.3 and earlier, the documentation can only be built against
-       PostgreSQL 9.6 or earlier.
-     </simpara>
-   </note>
-
-   <para>
-     To build the documentation as HTML, execute:
-   <programlisting>
-    ./configure &amp;&amp; make doc</programlisting>
-   </para>
-   <para>
-     The generated HTML files will be placed in the <filename>doc/html</filename>
-     subdirectory of your source tree.
-   </para>
-
-   <para>
-     To build the documentation as a single HTML file, after configuring and building
-     the main &repmgr; source as described above, execute:
-   <programlisting>
-     ./configure &amp;&amp; make doc-repmgr.html</programlisting>
-   </para>
-
-   <para>
-     To build the documentation as a PDF file, after configuring and building
-     the main &repmgr; source as described above, execute:
-   <programlisting>
-     ./configure &amp;&amp; make doc-repmgr-A4.pdf</programlisting>
-   </para>
-
-
- </sect2>
-
-</sect1>

doc/install.xml

@@ -1,29 +0,0 @@
-<chapter id="installation" xreflabel="Installation">
-
- <title>Installation</title>
-
- <indexterm>
-  <primary>installation</primary>
- </indexterm>
-
- <para>
-  &repmgr; can be installed from binary packages provided by your operating
-  system's packaging system, or from source.
- </para>
- <para>
-  In general we recommend using binary packages, unless unavailable for your operating system.
- </para>
- <para>
-  Source installs are mainly useful if you want to keep track of the very
-  latest repmgr development and contribute to development.  They're also the
-  only option if there are no packages for your operating system yet.
- </para>
- <para>
-  Before installing &repmgr; make sure you satisfy the <xref linkend="install-requirements"/>.
- </para>
-
- &install-requirements;
- &install-packages;
- &install-source;
-
-</chapter>

doc/legal.xml

@@ -1,37 +0,0 @@
-<!-- doc/legal.xml -->
-
-<date>2025</date>
-
-<copyright>
- <year>2010-2025</year>
- <holder>EDB</holder>
-</copyright>
-
-<legalnotice id="legalnotice">
- <title>Legal Notice</title>
-
- <para>
-  <productname>repmgr</productname> is Copyright &copy; 2010-2025
-  by EDB All rights reserved.
- </para>
-
- <para>
-   This program is free software: you can redistribute it and/or modify
-   it under the terms of the GNU General Public License as published by
-   the Free Software Foundation, either version 3 of the License, or
-   (at your option) any later version.
- </para>
- <para>
-   This program is distributed in the hope that it will be useful,
-   but WITHOUT ANY WARRANTY; without even the implied warranty of
-   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-   GNU General Public License for more details.
- </para>
- <para>
-   You should have received a copy of the GNU General Public License
-   along with this program.  If not, see
-   <ulink url="https://www.gnu.org/licenses/">https://www.gnu.org/licenses/</ulink>
-   to obtain one.
- </para>
-
-</legalnotice>

doc/overview.xml

@@ -1,241 +0,0 @@
-<chapter id="overview" xreflabel="Overview">
- <title>repmgr overview</title>
-
- <para>
-  This chapter provides a high-level overview of &repmgr;'s components and
-  functionality.
- </para>
- <sect1 id="repmgr-concepts" xreflabel="Concepts">
-
-  <title>Concepts</title>
-
-  <indexterm>
-    <primary>concepts</primary>
-  </indexterm>
-
-  <para>
-   This guide assumes that you are familiar with PostgreSQL administration and
-   streaming replication concepts. For further details on streaming
-   replication, see the PostgreSQL documentation section on <ulink
-   url="https://www.postgresql.org/docs/current/warm-standby.html#STREAMING-REPLICATION">
-   streaming replication</ulink>.
-  </para>
-  <para>
-   The following terms are used throughout the &repmgr; documentation.
-   <variablelist>
-    <varlistentry>
-     <term>replication cluster</term>
-     <listitem>
-      <simpara>
-       In the &repmgr; documentation, "replication cluster" refers to the network
-       of PostgreSQL servers connected by streaming replication.
-      </simpara>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>node</term>
-     <listitem>
-      <simpara>
-       A node is a single PostgreSQL server within a replication cluster.
-      </simpara>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>upstream node</term>
-     <listitem>
-      <simpara>
-       The node a standby server connects to, in order to receive streaming replication.
-       This is either the primary server, or in the case of cascading replication, another
-       standby.
-      </simpara>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>failover</term>
-     <listitem>
-      <simpara>
-       This is the action which occurs if a primary server fails and a suitable standby
-       is  promoted as the new primary. The &repmgrd; daemon supports automatic failover
-       to minimise downtime.
-      </simpara>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>switchover</term>
-     <listitem>
-      <simpara>
-       In certain circumstances, such as hardware or operating system maintenance,
-       it's necessary to take a primary server offline; in this case a controlled
-       switchover is necessary, whereby a suitable standby is promoted and the
-       existing primary removed from the replication cluster in a controlled manner.
-       The &repmgr; command line client provides this functionality.
-      </simpara>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>fencing</term>
-     <listitem>
-      <simpara>
-       In a failover situation, following the promotion of a new standby, it's
-       essential that the previous primary does not unexpectedly come back on
-       line, which would result in a split-brain situation. To prevent this,
-       the failed primary should be isolated from applications, i.e. "fenced off".
-      </simpara>
-     </listitem>
-    </varlistentry>
-   <varlistentry id="witness-server">
-     <term>witness server</term>
-     <listitem>
-      <para>
-        &repmgr; provides functionality to set up a so-called "witness server" to
-        assist in determining a new primary server in a failover situation with more
-        than one standby. The witness server itself is not part of the replication
-        cluster, although it does contain a copy of the repmgr metadata schema.
-      </para>
-      <para>
-        The purpose of a witness server is to provide a "casting vote" where servers
-        in the replication cluster are split over more than one location. In the event
-        of a loss of connectivity between locations, the presence or absence of
-        the witness server will decide whether a server at that location is promoted
-        to primary; this is to prevent a "split-brain" situation where an isolated
-        location interprets a network outage as a failure of the (remote) primary and
-        promotes a (local) standby.
-      </para>
-      <para>
-        A witness server only needs to be created if &repmgrd;
-        is in use.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </sect1>
- <sect1 id="repmgr-components" xreflabel="Components">
-  <title>Components</title>
-  <para>
-  &repmgr; is a suite of open-source tools to manage replication and failover
-  within a cluster of PostgreSQL servers. It supports and enhances PostgreSQL's
-  built-in streaming replication, which provides a single read/write primary server
-  and one or more read-only standbys containing near-real time copies of the primary
-  server's database. It provides two main tools:
-   <variablelist>
-    <varlistentry>
-     <term>repmgr</term>
-     <listitem>
-      <para>
-       A command-line tool used to perform administrative tasks such as:
-       <itemizedlist>
-        <listitem>
-          <simpara>setting up standby servers</simpara>
-        </listitem>
-        <listitem>
-          <simpara>promoting a standby server to primary</simpara>
-        </listitem>
-        <listitem>
-          <simpara>switching over primary and standby servers</simpara>
-        </listitem>
-        <listitem>
-          <simpara>displaying the status of servers in the replication cluster</simpara>
-        </listitem>
-       </itemizedlist>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>repmgrd</term>
-     <listitem>
-      <para>
-       A daemon which actively monitors servers in a replication cluster
-       and performs the following tasks:
-       <itemizedlist>
-        <listitem>
-          <simpara>monitoring and recording replication performance</simpara>
-        </listitem>
-        <listitem>
-          <simpara>performing failover by detecting failure of the primary and
-            promoting the most suitable standby server
-          </simpara>
-        </listitem>
-        <listitem>
-          <simpara>provide notifications about events in the cluster to a user-defined
-      script which can perform tasks such as sending alerts by email</simpara>
-        </listitem>
-       </itemizedlist>
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </sect1>
-
- <sect1 id="repmgr-user-metadata" xreflabel="Repmgr user and metadata">
-  <title>Repmgr user and metadata</title>
-  <para>
-   In order to effectively manage a replication cluster, &repmgr; needs to store
-   information about the servers in the cluster in a dedicated database schema.
-   This schema is automatically created by the &repmgr; extension, which is installed
-   during the first step in initializing a &repmgr;-administered cluster
-   (<command><link linkend="repmgr-primary-register">repmgr primary register</link></command>)
-   and contains the following objects:
-   <variablelist>
-    <varlistentry>
-     <term>Tables</term>
-     <listitem>
-      <para>
-       <itemizedlist>
-        <listitem>
-          <simpara><literal>repmgr.events</literal>: records events of interest</simpara>
-        </listitem>
-        <listitem>
-          <simpara><literal>repmgr.nodes</literal>: connection and status information for each server in the
-    replication cluster</simpara>
-        </listitem>
-        <listitem>
-          <simpara><literal>repmgr.monitoring_history</literal>: historical standby monitoring information
-            written by &repmgrd;</simpara>
-        </listitem>
-       </itemizedlist>
-      </para>
-     </listitem>
-    </varlistentry>
-    <varlistentry>
-     <term>Views</term>
-     <listitem>
-      <para>
-       <itemizedlist>
-        <listitem>
-          <simpara>repmgr.show_nodes: based on the table <literal>repmgr.nodes</literal>, additionally showing the
-           name of the server's upstream node</simpara>
-        </listitem>
-        <listitem>
-          <simpara>repmgr.replication_status: when &repmgrd;'s monitoring is enabled, shows
-            current monitoring status for each standby.</simpara>
-        </listitem>
-       </itemizedlist>
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   The &repmgr; metadata schema can be stored in an existing database or in its own
-   dedicated database. Note that the &repmgr; metadata schema cannot reside on a database
-   server which is not part of the replication cluster managed by &repmgr;.
-  </para>
-  <para>
-   A database user must be available for &repmgr; to access this database and perform
-   necessary changes. This user does not need to be a superuser, however some operations
-   such as initial installation of the &repmgr; extension will require a superuser
-   connection (this can be specified where required with the command line option
-   <literal>--superuser</literal>).
-  </para>
- </sect1>
-
-</chapter>

doc/promoting-standby.xml

@@ -1,79 +0,0 @@
-<chapter id="promoting-standby" xreflabel="Promoting a standby">
- <title>Promoting a standby server with repmgr</title>
- <indexterm>
-   <primary>promoting a standby</primary>
-   <seealso>repmgr standby promote</seealso>
- </indexterm>
- <para>
-   If a primary server fails or needs to be removed from the replication cluster,
-   a new primary server must be designated, to ensure the cluster continues
-   to function correctly. This can be done with <xref linkend="repmgr-standby-promote"/>,
-   which promotes the standby on the current server to primary.
- </para>
-
- <para>
-  To demonstrate this, set up a replication cluster with a primary and two attached
-  standby servers so that the cluster looks like this:
-  <programlisting>
-     $ repmgr -f /etc/repmgr.conf cluster show
-     ID | Name  | Role    | Status    | Upstream | Location | Connection string
-    ----+-------+---------+-----------+----------+----------+--------------------------------------
-     1  | node1 | primary | * running |          | default  | host=node1 dbname=repmgr user=repmgr
-     2  | node2 | standby |   running | node1    | default  | host=node2 dbname=repmgr user=repmgr
-     3  | node3 | standby |   running | node1    | default  | host=node3 dbname=repmgr user=repmgr</programlisting>
- </para>
- <para>
-  Stop the current primary with e.g.:
-  <programlisting>
-   $ pg_ctl -D /var/lib/postgresql/data -m fast stop</programlisting>
- </para>
- <para>
-  At this point the replication cluster will be in a partially disabled state, with
-  both standbys accepting read-only connections while attempting to connect to the
-  stopped primary. Note that the &repmgr; metadata table will not yet have been updated;
-  executing <xref linkend="repmgr-cluster-show"/> will note the discrepancy:
-  <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster show
-     ID | Name  | Role    | Status        | Upstream | Location | Connection string
-    ----+-------+---------+---------------+----------+----------+--------------------------------------
-     1  | node1 | primary | ? unreachable |          | default  | host=node1 dbname=repmgr user=repmgr
-     2  | node2 | standby |   running     | node1    | default  | host=node2 dbname=repmgr user=repmgr
-     3  | node3 | standby |   running     | node1    | default  | host=node3 dbname=repmgr user=repmgr
-
-    WARNING: following issues were detected
-    node "node1" (ID: 1) is registered as an active primary but is unreachable</programlisting>
- </para>
- <para>
-  Now promote the first standby with:
-  <programlisting>
-   $ repmgr -f /etc/repmgr.conf standby promote</programlisting>
- </para>
- <para>
-  This will produce output similar to the following:
-  <programlisting>
-    INFO: connecting to standby database
-    NOTICE: promoting standby
-    DETAIL: promoting server using "pg_ctl -l /var/log/postgresql/startup.log -w -D '/var/lib/postgresql/data' promote"
-    server promoting
-    INFO: reconnecting to promoted server
-    NOTICE: STANDBY PROMOTE successful
-    DETAIL: node 2 was successfully promoted to primary</programlisting>
- </para>
- <para>
-  Executing <xref linkend="repmgr-cluster-show"/> will show the current state; as there is now an
-  active primary, the previous warning will not be displayed:
-  <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster show
-     ID | Name  | Role    | Status    | Upstream | Location | Connection string
-    ----+-------+---------+-----------+----------+----------+--------------------------------------
-     1  | node1 | primary | - failed  |          | default  | host=node1 dbname=repmgr user=repmgr
-     2  | node2 | primary | * running |          | default  | host=node2 dbname=repmgr user=repmgr
-     3  | node3 | standby |   running | node1    | default  | host=node3 dbname=repmgr user=repmgr</programlisting>
- </para>
- <para>
-  However the sole remaining standby (<literal>node3</literal>) is still trying to replicate from the failed
-  primary; <xref linkend="repmgr-standby-follow"/> must now be executed to rectify this situation
-  (see <xref linkend="follow-new-primary"/> for example).
- </para>
-</chapter>
-

doc/quickstart.xml

@@ -1,515 +0,0 @@
-<chapter id="quickstart" xreflabel="Quick-start guide">
- <title>Quick-start guide</title>
-
- <indexterm>
-   <primary>quickstart</primary>
- </indexterm>
-
- <para>
-  This section gives a quick introduction to &repmgr;, including setting up a
-  sample &repmgr; installation and a basic replication cluster.
- </para>
- <para>
-  These instructions for demonstration purposes and are not suitable for a production
-  install, as issues such as account security considerations, and system administration
-  best practices are omitted.
- </para>
- <note>
-   <simpara>
-     To upgrade an existing &repmgr; 3.x installation, see section
-     <xref linkend="upgrading-from-repmgr-3"/>.
-   </simpara>
- </note>
-
- <sect1 id="quickstart-prerequisites">
-   <title>Prerequisites for setting up a basic replication cluster with &repmgr;</title>
-    <para>
-     The following section will describe how to set up a basic replication cluster
-     with a primary and a standby server using the <application>repmgr</application>
-     command line tool.
-    </para>
-    <para>
-      We'll assume the primary is called <literal>node1</literal> with IP address
-      <literal>192.168.1.11</literal>, and the standby is called <literal>node2</literal>
-      with IP address <literal>192.168.1.12</literal>
-    </para>
-    <para>
-     Following software must be installed on both servers:
-     <itemizedlist spacing="compact" mark="bullet">
-      <listitem>
-       <simpara><application>PostgreSQL</application></simpara>
-      </listitem>
-      <listitem>
-       <simpara>
-        <application>repmgr</application> (matching the installed
-        <application>PostgreSQL</application> major version)
-       </simpara>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-      At network level, connections between the PostgreSQL port (default: <literal>5432</literal>)
-      must be possible in both directions.
-    </para>
-    <para>
-      If you want <application>repmgr</application> to copy configuration files which are
-      located outside the PostgreSQL data directory, and/or to test
-      <command><link linkend="repmgr-standby-switchover">switchover</link></command>
-      functionality, you will also need passwordless SSH connections between both servers, and
-      <application>rsync</application> should be installed.
-    </para>
-    <tip>
-     <simpara>
-      For testing <application>repmgr</application>, it's possible to use multiple PostgreSQL
-      instances running on different ports on the same computer, with
-      passwordless SSH access to <filename>localhost</filename> enabled.
-     </simpara>
-    </tip>
- </sect1>
-
- <sect1 id="quickstart-postgresql-configuration" xreflabel="PostgreSQL configuration">
-   <title>PostgreSQL configuration</title>
-   <para>
-    On the primary server, a PostgreSQL instance must be initialised and running.
-    The following replication settings may need to be adjusted:
-   </para>
-   <programlisting>
-
-    # Enable replication connections; set this value to at least one more
-    # than the number of standbys which will connect to this server
-    # (note that repmgr will execute "pg_basebackup" in WAL streaming mode,
-    # which requires two free WAL senders).
-    #
-    # See: https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-WAL-SENDERS
-
-    max_wal_senders = 10
-
-    # If using replication slots, set this value to at least one more
-    # than the number of standbys which will connect to this server.
-    # Note that repmgr will only make use of replication slots if
-    # "use_replication_slots" is set to "true" in "repmgr.conf".
-    # (If you are not intending to use replication slots, this value
-    # can be set to "0").
-    #
-    # See: https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-MAX-REPLICATION-SLOTS
-
-    max_replication_slots = 10
-
-    # Ensure WAL files contain enough information to enable read-only queries
-    # on the standby.
-    #
-    #  PostgreSQL 9.5 and earlier: one of 'hot_standby' or 'logical'
-    #  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/runtime-config-wal.html#GUC-WAL-LEVEL
-
-    wal_level = 'hot_standby'
-
-    # Enable read-only queries on a standby
-    # (Note: this will be ignored on a primary but we recommend including
-    # it anyway, in case the primary later becomes a standby)
-    #
-    # See: https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-HOT-STANDBY
-
-    hot_standby = on
-
-    # Enable WAL file archiving
-    #
-    # See: https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-ARCHIVE-MODE
-
-    archive_mode = on
-
-    # Set archive command to a dummy command; this can later be changed without
-    # needing to restart the PostgreSQL instance.
-    #
-    # See: https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-ARCHIVE-COMMAND
-
-    archive_command = '/bin/true'
-   </programlisting>
-   <tip>
-    <simpara>
-      Rather than editing these settings in the default <filename>postgresql.conf</filename>
-      file, create a separate file such as <filename>postgresql.replication.conf</filename> and
-      include it from the end of the main configuration file with:
-     <command>include 'postgresql.replication.conf'</command>.
-    </simpara>
-   </tip>
-   <para>
-     Additionally, if you are intending to use <application>pg_rewind</application>,
-     and the cluster was not initialised using data checksums, you may want to consider enabling
-     <varname>wal_log_hints</varname>; for more details see <xref linkend="repmgr-node-rejoin-pg-rewind"/>.
-   </para>
-    <para>
-      See also the <link linkend="configuration-postgresql">PostgreSQL configuration</link> section in the
-      <link linkend="configuration">repmgr configuration guide</link>.
-    </para>
- </sect1>
-
- <sect1 id="quickstart-repmgr-user-database">
-  <title>Create the repmgr user and database</title>
-  <para>
-   Create a dedicated PostgreSQL superuser account and a database for
-   the &repmgr; metadata, e.g.
-  </para>
-  <programlisting>
-   createuser -s repmgr
-   createdb repmgr -O repmgr
-  </programlisting>
-
-  <para>
-   For the examples in this document, the name <literal>repmgr</literal> will be
-   used for both user and database, but any names can be used.
-  </para>
-  <note>
-   <para>
-    For the sake of simplicity, the <literal>repmgr</literal> user is created
-    as a superuser. If desired, it's possible to create the <literal>repmgr</literal>
-    user as a normal user. However for certain operations superuser permissions
-    are required; in this case the command line option <command>--superuser</command>
-    can be provided to specify a superuser.
-   </para>
-   <para>
-    It's also assumed that the <literal>repmgr</literal> user will be used to make the
-    replication connection from the standby to the primary; again this can be
-    overridden by specifying a separate replication user when registering each node.
-   </para>
-  </note>
-
-  <tip>
-    <para>
-     &repmgr; will install the <literal>repmgr</literal> extension, which creates a
-     <literal>repmgr</literal> schema containing the &repmgr;'s metadata tables as
-     well as other functions and views. We also recommend that you set the
-     <literal>repmgr</literal> user's search path to include this schema name, e.g.
-     <programlisting>
-       ALTER USER repmgr SET search_path TO repmgr, "$user", public;</programlisting>
-    </para>
-  </tip>
-
- </sect1>
-
- <sect1 id="quickstart-authentication">
-  <title>Configuring authentication in pg_hba.conf</title>
-  <para>
-   Ensure the <literal>repmgr</literal> user has appropriate permissions in <filename>pg_hba.conf</filename> and
-   can connect in replication mode; <filename>pg_hba.conf</filename> should contain entries
-   similar to the following:
-  </para>
-  <programlisting>
-    local   replication   repmgr                              trust
-    host    replication   repmgr      127.0.0.1/32            trust
-    host    replication   repmgr      192.168.1.0/24          trust
-
-    local   repmgr        repmgr                              trust
-    host    repmgr        repmgr      127.0.0.1/32            trust
-    host    repmgr        repmgr      192.168.1.0/24          trust
-  </programlisting>
-  <para>
-   Note that these are simple settings for testing purposes.
-   Adjust according to your network environment and authentication requirements.
-  </para>
- </sect1>
-
- <sect1 id="quickstart-standby-preparation">
-  <title>Preparing the standby</title>
-  <para>
-   On the standby, do <emphasis>not</emphasis> create a PostgreSQL instance (i.e.
-   do not execute <application>initdb</application> or any database creation
-   scripts provided by packages), but do ensure the destination
-   data directory (and any other directories which you want PostgreSQL to use)
-   exist and are owned by the <literal>postgres</literal> system user. Permissions
-   must be set to <literal>0700</literal> (<literal>drwx------</literal>).
-  </para>
-  <tip>
-    <simpara>
-      &repmgr; will place a copy of the primary's database files in this directory.
-      It will however refuse to run if a PostgreSQL instance has already been
-      created there.
-    </simpara>
-  </tip>
-  <para>
-   Check the primary database is reachable from the standby using <application>psql</application>:
-  </para>
-  <programlisting>
-    psql 'host=node1 user=repmgr dbname=repmgr connect_timeout=2'</programlisting>
-
-  <note>
-   <para>
-    &repmgr; stores connection information as <ulink
-    url="https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING">libpq
-    connection strings</ulink> throughout. This documentation refers to them as <literal>conninfo</literal>
-    strings; an alternative name is <literal>DSN</literal> (<literal>data source name</literal>).
-    We'll use these in place of the <command>-h hostname -d databasename -U username</command> syntax.
-   </para>
-  </note>
- </sect1>
-
- <sect1 id="quickstart-repmgr-conf">
-  <title>repmgr configuration file</title>
-  <para>
-   Create a <filename>repmgr.conf</filename> file on the primary server. The file must
-   contain at least the following parameters:
-  </para>
-  <programlisting>
-    node_id=1
-    node_name='node1'
-    conninfo='host=node1 user=repmgr dbname=repmgr connect_timeout=2'
-    data_directory='/var/lib/postgresql/data'
-  </programlisting>
-
-  <para>
-   <filename>repmgr.conf</filename> should not be stored inside the PostgreSQL data directory,
-   as it could be overwritten when setting up or reinitialising the PostgreSQL
-   server. See sections <xref linkend="configuration"/> and <xref linkend="configuration-file"/>
-   for further details about <filename>repmgr.conf</filename>.
-  </para>
-  <note>
-    <para>
-      &repmgr; only uses <option>pg_bindir</option> when it executes
-      PostgreSQL binaries directly.
-    </para>
-    <para>
-      For user-defined scripts such as <option>promote_command</option> and the
-      various <option>service_*_command</option>s, you <emphasis>must</emphasis>
-      always explicitly provide the full path to the binary or script being
-      executed, even if it is &repmgr; itself.
-    </para>
-    <para>
-      This is because these options can contain user-defined scripts in arbitrary
-      locations, so prepending <option>pg_bindir</option> may break them.
-    </para>
-  </note>
-
-  <tip>
-   <simpara>
-    For Debian-based distributions we recommend explicitly setting
-    <option>pg_bindir</option> to the directory where <command>pg_ctl</command> and other binaries
-    not in the standard path are located. For PostgreSQL 9.6 this would be <filename>/usr/lib/postgresql/9.6/bin/</filename>.
-   </simpara>
-  </tip>
-
-  <tip>
-    <simpara>
-      If your distribution places the &repmgr; binaries in a location other than the
-      PostgreSQL installation directory, specify this with <option>repmgr_bindir</option>
-      to enable &repmgr; to perform operations (e.g.
-      <command><link linkend="repmgr-cluster-crosscheck">repmgr cluster crosscheck</link></command>)
-      on other nodes.
-    </simpara>
-  </tip>
-
-  <para>
-   See the file
-   <ulink url="https://raw.githubusercontent.com/EnterpriseDB/repmgr/master/repmgr.conf.sample">repmgr.conf.sample</ulink>
-    for details of all available configuration parameters.
-  </para>
-
- </sect1>
-
-
- <sect1 id="quickstart-primary-register">
-  <title>Register the primary server</title>
-  <para>
-   To enable &repmgr; to support a replication cluster, the primary node must
-   be registered with &repmgr;. This installs the <literal>repmgr</literal>
-   extension and metadata objects, and adds a metadata record for the primary server:
-  </para>
-
-  <programlisting>
-    $ repmgr -f /etc/repmgr.conf primary register
-    INFO: connecting to primary database...
-    NOTICE: attempting to install extension "repmgr"
-    NOTICE: "repmgr" extension successfully installed
-    NOTICE: primary node record (id: 1) registered</programlisting>
-
-  <para>
-    Verify status of the cluster like this:
-  </para>
-  <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster show
-     ID | Name  | Role    | Status    | Upstream | Connection string
-    ----+-------+---------+-----------+----------+--------------------------------------------------------
-     1  | node1 | primary | * running |          | host=node1 dbname=repmgr user=repmgr connect_timeout=2
-  </programlisting>
-  <para>
-    The record in the <literal>repmgr</literal> metadata table will look like this:
-  </para>
-  <programlisting>
-    repmgr=# SELECT * FROM repmgr.nodes;
-    -[ RECORD 1 ]----+-------------------------------------------------------
-    node_id          | 1
-    upstream_node_id |
-    active           | t
-    node_name        | node1
-    type             | primary
-    location         | default
-    priority         | 100
-    conninfo         | host=node1 dbname=repmgr user=repmgr connect_timeout=2
-    repluser         | repmgr
-    slot_name        |
-    config_file      | /etc/repmgr.conf</programlisting>
-  <para>
-    Each server in the replication cluster will have its own record. If &repmgrd;
-    is in use, the fields <literal>upstream_node_id</literal>, <literal>active</literal> and
-    <literal>type</literal> will be updated when the node's status or role changes.
-  </para>
- </sect1>
-
- <sect1 id="quickstart-standby-clone">
-  <title>Clone the standby server</title>
-  <para>
-   Create a <filename>repmgr.conf</filename> file on the standby server. It must contain at
-   least the same parameters as the primary's <filename>repmgr.conf</filename>, but with
-   the mandatory values <literal>node</literal>, <literal>node_name</literal>, <literal>conninfo</literal>
-   (and possibly <literal>data_directory</literal>) adjusted accordingly, e.g.:
-  </para>
-  <programlisting>
-    node_id=2
-    node_name='node2'
-    conninfo='host=node2 user=repmgr dbname=repmgr connect_timeout=2'
-    data_directory='/var/lib/postgresql/data'</programlisting>
-  <para>
-   Use the <command>--dry-run</command> option to check the standby can be cloned:
-  </para>
-  <programlisting>
-    $ repmgr -h node1 -U repmgr -d repmgr -f /etc/repmgr.conf standby clone --dry-run
-    NOTICE: using provided configuration file "/etc/repmgr.conf"
-    NOTICE: destination directory "/var/lib/postgresql/data" provided
-    INFO: connecting to source node
-    NOTICE: checking for available walsenders on source node (2 required)
-    INFO: sufficient walsenders available on source node (2 required)
-    NOTICE: standby will attach to upstream node 1
-    HINT: consider using the -c/--fast-checkpoint option
-    INFO: all prerequisites for "standby clone" are met</programlisting>
-  <para>
-    If no problems are reported, the standby can then be cloned with:
-  </para>
-  <programlisting>
-    $ repmgr -h node1 -U repmgr -d repmgr -f /etc/repmgr.conf standby clone
-
-    NOTICE: using configuration file "/etc/repmgr.conf"
-    NOTICE: destination directory "/var/lib/postgresql/data" provided
-    INFO: connecting to source node
-    NOTICE: checking for available walsenders on source node (2 required)
-    INFO: sufficient walsenders available on source node (2 required)
-    INFO: creating directory "/var/lib/postgresql/data"...
-    NOTICE: starting backup (using pg_basebackup)...
-    HINT: this may take some time; consider using the -c/--fast-checkpoint option
-    INFO: executing:
-      pg_basebackup -l "repmgr base backup" -D /var/lib/postgresql/data -h node1 -U repmgr -X stream
-    NOTICE: standby clone (using pg_basebackup) complete
-    NOTICE: you can now start your PostgreSQL server
-    HINT: for example: pg_ctl -D /var/lib/postgresql/data start
-  </programlisting>
-  <para>
-   This has cloned the PostgreSQL data directory files from the primary <literal>node1</literal>
-   using PostgreSQL's <command>pg_basebackup</command> utility. Replication configuration
-   containing the correct parameters to start streaming from this primary server will be
-   automatically appended to <filename>postgresql.auto.conf</filename>. (In PostgreSQL 11
-   and earlier the file <filename>recovery.conf</filename> will be created).
-  </para>
-  <note>
-   <simpara>
-    By default, any configuration files in the primary's data directory will be
-    copied to the standby. Typically these will be <filename>postgresql.conf</filename>,
-    <filename>postgresql.auto.conf</filename>, <filename>pg_hba.conf</filename> and
-    <filename>pg_ident.conf</filename>. These may require modification before the standby
-    is started.
-   </simpara>
-  </note>
-  <para>
-   Make any adjustments to the standby's PostgreSQL configuration files now,
-   then start the server.
-  </para>
-  <para>
-   For more details on <command>repmgr standby clone</command>, see the
-   <link linkend="repmgr-standby-clone">command reference</link>.
-   A more detailed overview of cloning options is available in the
-   <link linkend="cloning-standbys">administration manual</link>.
-  </para>
- </sect1>
-
- <sect1 id="quickstart-verify-replication">
-  <title>Verify replication is functioning</title>
-  <para>
-   Connect to the primary server and execute:
-   <programlisting>
-    repmgr=# SELECT * FROM pg_stat_replication;
-    -[ RECORD 1 ]----+------------------------------
-    pid              | 19111
-    usesysid         | 16384
-    usename          | repmgr
-    application_name | node2
-    client_addr      | 192.168.1.12
-    client_hostname  |
-    client_port      | 50378
-    backend_start    | 2017-08-28 15:14:19.851581+09
-    backend_xmin     |
-    state            | streaming
-    sent_location    | 0/7000318
-    write_location   | 0/7000318
-    flush_location   | 0/7000318
-    replay_location  | 0/7000318
-    sync_priority    | 0
-    sync_state       | async</programlisting>
-   This shows that the previously cloned standby (<literal>node2</literal> shown in the field
-   <literal>application_name</literal>) has connected to the primary from IP address
-   <literal>192.168.1.12</literal>.
-  </para>
-  <para>
-    From PostgreSQL 9.6 you can also use the view
-    <ulink url="https://www.postgresql.org/docs/current/monitoring-stats.html#PG-STAT-WAL-RECEIVER-VIEW">
-    <literal>pg_stat_wal_receiver</literal></ulink> to check the replication status from the standby.
-
-   <programlisting>
-    repmgr=# SELECT * FROM pg_stat_wal_receiver;
-    Expanded display is on.
-    -[ RECORD 1 ]---------+--------------------------------------------------------------------------------
-    pid                   | 18236
-    status                | streaming
-    receive_start_lsn     | 0/3000000
-    receive_start_tli     | 1
-    received_lsn          | 0/7000538
-    received_tli          | 1
-    last_msg_send_time    | 2017-08-28 15:21:26.465728+09
-    last_msg_receipt_time | 2017-08-28 15:21:26.465774+09
-    latest_end_lsn        | 0/7000538
-    latest_end_time       | 2017-08-28 15:20:56.418735+09
-    slot_name             |
-    sender_host           | node1
-    sender_port           | 5432
-    conninfo              | user=repmgr dbname=replication host=node1 application_name=node2
-   </programlisting>
-   Note that the <varname>conninfo</varname> value is that generated in <filename>postgresql.auto.conf</filename>
-   (PostgreSQL 11 and earlier: <filename>recovery.conf</filename>) and will differ slightly from the primary's
-   <varname>conninfo</varname> as set in <filename>repmgr.conf</filename> - among others it will contain the
-   connecting node's name as <varname>application_name</varname>.
-  </para>
- </sect1>
-
- <sect1 id="quickstart-register-standby">
-  <title>Register the standby</title>
-  <para>
-    Register the standby server with:
-    <programlisting>
-    $ repmgr -f /etc/repmgr.conf standby register
-    NOTICE: standby node "node2" (ID: 2) successfully registered</programlisting>
-  </para>
-  <para>
-    Check the node is registered by executing <command>repmgr cluster show</command> on the standby:
-    <programlisting>
-      $ repmgr -f /etc/repmgr.conf cluster show
-
-     ID | Name  | Role    | Status    | Upstream | Location | Priority | Timeline | Connection string
-    ----+-------+---------+-----------+----------+----------+----------+----------+--------------------------------------
-     1  | node1 | primary | * running |          | default  | 100      | 1        | host=node1 dbname=repmgr user=repmgr
-     2  | node2 | standby |   running | node1    | default  | 100      | 1        | host=node2 dbname=repmgr user=repmgr</programlisting>
-  </para>
-  <para>
-   Both nodes are now registered with &repmgr; and the records have been copied to the standby server.
-  </para>
- </sect1>
-
-</chapter>

doc/repmgr-cluster-cleanup.xml

@@ -1,77 +0,0 @@
-<refentry id="repmgr-cluster-cleanup">
-  <indexterm>
-    <primary>repmgr cluster cleanup</primary>
-  </indexterm>
- <refmeta>
-    <refentrytitle>repmgr cluster cleanup</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr cluster cleanup</refname>
-    <refpurpose>purge monitoring history</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      Purges monitoring history from the <literal>repmgr.monitoring_history</literal> table to
-      prevent excessive table growth.
-    </para>
-    <para>
-      By default <emphasis>all</emphasis> data will be removed; Use the <option>-k/--keep-history</option>
-      option to specify the number of days of monitoring history to retain.
-    </para>
-    <para>
-      This command can be executed manually or as a cronjob.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Usage</title>
-    <para>
-      This command requires a valid <filename>repmgr.conf</filename> file for the node on which it is
-      executed; no additional arguments are required.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Notes</title>
-
-    <para>
-      Monitoring history will only be written if &repmgrd; is active, and
-      <varname>monitoring_history</varname> is set to <literal>true</literal> in
-      <filename>repmgr.conf</filename>.
-    </para>
-  </refsect1>
-
-  <refsect1 id="repmgr-cluster-cleanup-events">
-    <title>Event notifications</title>
-    <para>
-      A <literal>cluster_cleanup</literal> <link linkend="event-notifications">event notification</link> will be generated.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Options</title>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--node-id</option></term>
-        <listitem>
-          <para>
-            Only delete monitoring records for the specified node.
-          </para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-      For more details see the sections <xref linkend="repmgrd-monitoring"/> and
-      <xref linkend="repmgrd-monitoring-configuration"/>.
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr-cluster-crosscheck.xml

@@ -1,96 +0,0 @@
-<refentry id="repmgr-cluster-crosscheck">
-  <indexterm>
-    <primary>repmgr cluster crosscheck</primary>
-  </indexterm>
-
-
-  <refmeta>
-    <refentrytitle>repmgr cluster crosscheck</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr cluster crosscheck</refname>
-    <refpurpose>cross-checks connections between each combination of nodes</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      <command>repmgr cluster crosscheck</command> is similar to <xref linkend="repmgr-cluster-matrix"/>,
-        but cross-checks connections between each combination of nodes. In "Example 3" in
-        <xref linkend="repmgr-cluster-matrix"/> we have no information about the state of <literal>node3</literal>.
-        However by running <command>repmgr cluster crosscheck</command> it's possible to get a better
-        overview of the cluster situation:
-          <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster crosscheck
-
-    Name   | Id |  1 |  2 |  3
-    -------+----+----+----+----
-     node1 |  1 |  * |  * |  x
-     node2 |  2 |  * |  * |  *
-     node3 |  3 |  * |  * |  *</programlisting>
-    </para>
-    <para>
-      What happened is that <command>repmgr cluster crosscheck</command> merged its own
-      <command><link linkend="repmgr-cluster-matrix">repmgr cluster matrix</link></command> with the
-      <command>repmgr cluster matrix</command> output from <literal>node2</literal>; the latter is
-      able to connect to <literal>node3</literal>
-      and therefore determine the state of outbound connections from that node.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr cluster crosscheck</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            The check completed successfully and all nodes are reachable.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_BAD_SSH (12)</option></term>
-        <listitem>
-          <para>
-            One or more nodes could not be accessed via SSH.
-          </para>
-          <note>
-            <simpara>
-              This only applies to nodes unreachable from the node where
-              this command is executed.
-            </simpara>
-            <simpara>
-              It's also possible that the crosscheck establishes that
-              connections between PostgreSQL on all nodes are functioning,
-              even if SSH access between some nodes is not possible.
-            </simpara>
-          </note>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_NODE_STATUS (25)</option></term>
-        <listitem>
-          <para>
-            PostgreSQL on one or more nodes could not be reached.
-          </para>
-          <note>
-            <simpara>
-              This error code overrides <option>ERR_BAD_SSH</option>.
-            </simpara>
-          </note>
-        </listitem>
-      </varlistentry>
-
-   </variablelist>
-  </refsect1>
-
-</refentry>
-

doc/repmgr-cluster-event.xml

@@ -1,79 +0,0 @@
-<refentry id="repmgr-cluster-event">
-  <indexterm>
-    <primary>repmgr cluster event</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr cluster event</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr cluster event</refname>
-    <refpurpose>output a formatted list of cluster events</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-
-    <para>
-      Outputs a formatted list of cluster events, as stored in the <literal>repmgr.events</literal> table.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Usage</title>
-
-    <para>
-      Output is in reverse chronological order, and
-      can be filtered with the following options:
-      <itemizedlist spacing="compact" mark="bullet">
-        <listitem>
-          <simpara><literal>--all</literal>: outputs all entries</simpara>
-        </listitem>
-        <listitem>
-          <simpara><literal>--limit</literal>: set the maximum number of entries to output (default: 20)</simpara>
-        </listitem>
-        <listitem>
-          <simpara><literal>--node-id</literal>: restrict entries to node with this ID</simpara>
-        </listitem>
-        <listitem>
-          <simpara><literal>--node-name</literal>: restrict entries to node with this name</simpara>
-        </listitem>
-        <listitem>
-          <simpara><literal>--event</literal>: filter specific event (see <xref linkend="event-notifications"/> for a full list)</simpara>
-        </listitem>
-      </itemizedlist>
-    </para>
-    <para>
-      The &quot;Details&quot; column can be omitted by providing <literal>--compact</literal>.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Output format</title>
-    <para>
-      <itemizedlist spacing="compact" mark="bullet">
-
-        <listitem>
-          <simpara>
-            <literal>--csv</literal>: generate output in CSV format. Note that the <literal>Details</literal>
-            column will currently not be emitted in CSV format.
-          </simpara>
-        </listitem>
-
-      </itemizedlist>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Example</title>
-    <para>
-      <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster event --event=standby_register
-     Node ID | Name  | Event            | OK | Timestamp           | Details
-    ---------+-------+------------------+----+---------------------+-------------------------------------------------------
-     3       | node3 | standby_register | t  | 2019-04-16 10:59:59 | standby registration succeeded; upstream node ID is 1
-     2       | node2 | standby_register | t  | 2019-04-16 10:59:57 | standby registration succeeded; upstream node ID is 1</programlisting>
-    </para>
-  </refsect1>
-</refentry>

doc/repmgr-cluster-matrix.xml

@@ -1,145 +0,0 @@
-<refentry id="repmgr-cluster-matrix">
-  <indexterm>
-    <primary>repmgr cluster matrix</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr cluster matrix</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr cluster matrix</refname>
-    <refpurpose>
-      runs repmgr cluster show on each node and summarizes output
-    </refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      <command>repmgr cluster matrix</command> runs <command><link linkend="repmgr-cluster-show">repmgr cluster show</link></command> on each
-      node and arranges the results in a matrix, recording success or failure.
-    </para>
-    <para>
-      <command>repmgr cluster matrix</command> requires a valid <filename>repmgr.conf</filename>
-      file on each node. Additionally, passwordless <command>ssh</command> connections are required between
-      all nodes.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Example</title>
-    <para>
-    Example 1 (all nodes up):
-    <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster matrix
-
-    Name   | Id |  1 |  2 |  3
-    -------+----+----+----+----
-     node1 |  1 |  * |  * |  *
-     node2 |  2 |  * |  * |  *
-     node3 |  3 |  * |  * |  *</programlisting>
-  </para>
-  <para>
-    Example 2 (<literal>node1</literal> and <literal>node2</literal> up, <literal>node3</literal> down):
-    <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster matrix
-
-    Name   | Id |  1 |  2 |  3
-    -------+----+----+----+----
-     node1 |  1 |  * |  * |  x
-     node2 |  2 |  * |  * |  x
-     node3 |  3 |  ? |  ? |  ?
-    </programlisting>
-  </para>
-  <para>
-   Each row corresponds to one server, and indicates the result of
-   testing an outbound connection from that server.
-  </para>
-  <para>
-    Since <literal>node3</literal> is down, all the entries in its row are filled with
-    <literal>?</literal>, meaning that there we cannot test outbound connections.
-  </para>
-  <para>
-    The other two nodes are up; the corresponding rows have <literal>x</literal> in the
-    column corresponding to <literal>node3</literal>, meaning that inbound connections to
-    that node have failed, and <literal>*</literal> in the columns corresponding to
-    <literal>node1</literal> and <literal>node2</literal>, meaning that inbound connections
-    to these nodes have succeeded.
-  </para>
-  <para>
-    Example 3 (all nodes up, firewall dropping packets originating
-    from <literal>node1</literal> and directed to port 5432 on <literal>node3</literal>) -
-    running <command>repmgr cluster matrix</command> from <literal>node1</literal> gives the following output:
-    <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster matrix
-
-    Name   | Id |  1 |  2 |  3
-    -------+----+----+----+----
-     node1 |  1 |  * |  * |  x
-     node2 |  2 |  * |  * |  *
-     node3 |  3 |  ? |  ? |  ?</programlisting>
-  </para>
-  <para>
-    Note this may take some time depending on the <varname>connect_timeout</varname>
-    setting in the node <varname>conninfo</varname> strings; default is
-    <literal>1 minute</literal> which means without modification the above
-    command would take around 2 minutes to run; see comment elsewhere about setting
-    <varname>connect_timeout</varname>)
-  </para>
-  <para>
-   The matrix tells us that we cannot connect from <literal>node1</literal> to <literal>node3</literal>,
-   and that (therefore) we don't know the state of any outbound
-   connection from <literal>node3</literal>.
-  </para>
-  <para>
-    In this case, the <xref linkend="repmgr-cluster-crosscheck"/> command will produce a more
-    useful result.
-  </para>
-  </refsect1>
-
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr cluster matrix</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            The check completed successfully and all nodes are reachable.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_BAD_SSH (12)</option></term>
-        <listitem>
-          <para>
-            One or more nodes could not be accessed via SSH.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_NODE_STATUS (25)</option></term>
-        <listitem>
-          <para>
-            PostgreSQL on one or more nodes could not be reached.
-          </para>
-          <note>
-            <simpara>
-              This error code overrides <option>ERR_BAD_SSH</option>.
-            </simpara>
-          </note>
-        </listitem>
-      </varlistentry>
-
-   </variablelist>
-  </refsect1>
-
-</refentry>
-

doc/repmgr-cluster-show.xml

@@ -1,245 +0,0 @@
-<refentry id="repmgr-cluster-show">
-  <indexterm>
-    <primary>repmgr cluster show</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr cluster show</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr cluster show</refname>
-    <refpurpose>display information about each registered node in the replication cluster</refpurpose>
-  </refnamediv>
-
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      Displays information about each registered node in the replication cluster. This
-      command polls each registered server and shows its role (<literal>primary</literal> /
-      <literal>standby</literal>) and status. It polls each server
-      directly and can be run on any node in the cluster; this is also useful when analyzing
-      connectivity from a particular node.
-    </para>
-	<para>
-	  For PostgreSQL 9.6 and later, the output will also contain the node's current timeline ID.
-	</para>
-    <para>
-      Node availability is tested by connecting from the node where
-      <command>repmgr cluster show</command> is executed, and does not necessarily imply the node
-      is down. See <xref linkend="repmgr-cluster-matrix"/> and <xref linkend="repmgr-cluster-crosscheck"/> to get
-      better overviews of connections between nodes.
-    </para>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Execution</title>
-    <para>
-      This command requires either a valid <filename>repmgr.conf</filename> file or a database
-      connection string to one of the registered nodes; no additional arguments are needed.
-    </para>
-
-    <para>
-      To show database connection errors when polling nodes, run the command in
-      <literal>--verbose</literal> mode.
-    </para>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Example</title>
-    <para>
-    <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster show
-     ID | Name  | Role    | Status    | Upstream | Location | Priority | Timeline | Connection string
-    ----+-------+---------+-----------+----------+----------+----------+----------+-----------------------------------------
-     1  | node1 | primary | * running |          | default  | 100      | 1        | host=db_node1 dbname=repmgr user=repmgr
-     2  | node2 | standby |   running | node1    | default  | 100      | 1        | host=db_node2 dbname=repmgr user=repmgr
-     3  | node3 | standby |   running | node1    | default  | 100      | 1        | host=db_node3 dbname=repmgr user=repmgr
-     4  | node4 | standby |   running | node1    | default  | 100      | 1        | host=db_node4 dbname=repmgr user=repmgr
-     5  | node5 | witness | * running | node1    | default  | 0        | n/a      | host=db_node5 dbname=repmgr user=repmgr</programlisting>
-  </para>
-  </refsect1>
-  <refsect1>
-    <title>Notes</title>
-    <para>
-      The column <literal>Role</literal> shows the expected server role according to the
-      &repmgr; metadata.
-	</para>
-	<para>
-	  <literal>Status</literal> shows whether the server is running or unreachable.
-      If the node has an unexpected role not reflected in the &repmgr; metadata, e.g. a node was manually
-      promoted to primary, this will be highlighted with an exclamation mark.
-	  If a connection to the node cannot be made, this will be highlighted with a question mark.
-	  Note that the node will only be shown as <literal>? unreachable</literal>
-	  if a connection is not possible at network level; if the PostgreSQL instance on the
-	  node is pingable but not accepting connections, it will be shown as <literal>? running</literal>.
-	</para>
-	<para>
-	  In the following example, executed on <literal>node3</literal>, <literal>node1</literal> is not reachable
-	  at network level and assumed to be down; <literal>node2</literal> has been promoted to primary
-	  (but <literal>node3</literal> is not attached to it, and its metadata has not yet been updated);
-	  <literal>node4</literal> is running but rejecting connections (from <literal>node3</literal> at least).
-      <programlisting>
-     ID | Name  | Role    | Status               | Upstream | Location | Priority | Timeline | Connection string
-    ----+-------+---------+----------------------+----------+----------+----------+----------+----------------------------------------------------
-     1  | node1 | primary | ? unreachable        |          | default  | 100      |          | host=db_node1 dbname=repmgr user=repmgr
-     2  | node2 | standby | ! running as primary | ? node1  | default  | 100      | 2        | host=db_node2 dbname=repmgr user=repmgr
-     3  | node3 | standby |   running            | ? node1  | default  | 100      | 1        | host=db_node3 dbname=repmgr user=repmgr
-     4  | node4 | standby | ? running            | ? node1  | default  | 100      |          | host=db_node4 dbname=repmgr user=repmgr
-
-    WARNING: following issues were detected
-      - unable to connect to node "node1" (ID: 1)
-      - node "node1" (ID: 1) is registered as an active primary but is unreachable
-      - node "node2" (ID: 2) is registered as standby but running as primary
-      - unable to connect to node "node2" (ID: 2)'s upstream node "node1" (ID: 1)
-      - unable to determine if node "node2" (ID: 2) is attached to its upstream node "node1" (ID: 1)
-      - unable to connect to node "node3" (ID: 3)'s upstream node "node1" (ID: 1)
-      - unable to determine if node "node3" (ID: 3) is attached to its upstream node "node1" (ID: 1)
-      - unable to connect to node "node4" (ID: 4)
-    HINT: execute with --verbose option to see connection error messages</programlisting>
-    </para>
-	<para>
-	  To diagnose connection issues, execute <command>repmgr cluster show</command>
-	  with the <option>--verbose</option> option; this will display the error message
-	  for each failed connection attempt.
-	</para>
-	<tip>
-	  <para>
-		Use <xref linkend="repmgr-cluster-matrix"/> and <xref linkend="repmgr-cluster-crosscheck"/>
-		to diagnose connection issues across the whole replication cluster.
-	  </para>
-	</tip>
-  </refsect1>
-
-  <refsect1>
-    <title>Options</title>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--csv</option></term>
-        <listitem>
-	  <para>
-	    <command>repmgr cluster show</command> accepts an optional parameter <literal>--csv</literal>, which
-	    outputs the replication cluster's status in a simple CSV format, suitable for
-	    parsing by scripts, e.g.:
-	    <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster show --csv
-    1,-1,-1
-    2,0,0
-    3,0,1</programlisting>
-	  </para>
-	  <para>
-	    The columns have following meanings:
-	    <itemizedlist spacing="compact" mark="bullet">
-	      <listitem>
-		<simpara>
-		  node ID
-		</simpara>
-	      </listitem>
-	      <listitem>
-		<simpara>
-            availability (0 = available, -1 = unavailable)
-		</simpara>
-	      </listitem>
-	      <listitem>
-		<simpara>
-            recovery state (0 = not in recovery, 1 = in recovery, -1 = unknown)
-		</simpara>
-	      </listitem>
-	    </itemizedlist>
-	  </para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--compact</option></term>
-        <listitem>
-          <para>
-			Suppress display of the <literal>conninfo</literal> column.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--terse</option></term>
-        <listitem>
-          <para>
-			Suppress warnings about connection issues.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--verbose</option></term>
-        <listitem>
-          <para>
-			Display the full text of any database connection error messages
-          </para>
-        </listitem>
-      </varlistentry>
-
-	</variablelist>
-
-  </refsect1>
-
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr cluster show</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            No issues were detected.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_BAD_CONFIG (1)</option></term>
-        <listitem>
-          <para>
-            An issue was encountered while attempting to retrieve
-            &repmgr; metadata.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_DB_CONN (6)</option></term>
-        <listitem>
-          <para>
-            &repmgr; was unable to connect to the local PostgreSQL instance.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_NODE_STATUS (25)</option></term>
-        <listitem>
-          <para>
-            One or more issues were detected with the replication configuration,
-            e.g. a node was not in its expected state.
-          </para>
-        </listitem>
-      </varlistentry>
-
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-     <xref linkend="repmgr-node-status"/>, <xref linkend="repmgr-node-check"/>, <xref linkend="repmgr-service-status"/>
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr-daemon-start.xml

@@ -1,208 +0,0 @@
-<refentry id="repmgr-daemon-start">
-  <indexterm>
-    <primary>repmgr daemon start</primary>
-  </indexterm>
-
-  <indexterm>
-    <primary>repmgrd</primary>
-    <secondary>starting</secondary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr daemon start</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr daemon start</refname>
-    <refpurpose>Start the &repmgrd; daemon on the local node</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      This command starts the &repmgrd; service on the
-      local node.
-    </para>
-    <para>
-      By default, &repmgr; will wait for up to 15 seconds to confirm that &repmgrd;
-      started. This behaviour can be overridden by specifying a different value using the <option>--wait</option>
-      option, or disabled altogether with the <option>--no-wait</option> option.
-    </para>
-
-    <important>
-      <para>
-        The <filename>repmgr.conf</filename> parameter <varname>repmgrd_service_start_command</varname>
-        must be set for <command>repmgr daemon start</command> to work; see section
-        <xref linkend="repmgr-daemon-start-configuration"/> for details.
-      </para>
-    </important>
-  </refsect1>
-
-
-
-  <refsect1>
-
-    <title>Options</title>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually attempt to start &repmgrd;.
-          </para>
-          <para>
-            This action will output the command which would be executed.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>-w</option></term>
-        <term><option>--wait</option></term>
-        <listitem>
-          <para>
-            Wait for the specified number of seconds to confirm that &repmgrd;
-            started successfully.
-          </para>
-          <para>
-            Note that providing <option>--wait=0</option> is the equivalent of <option>--no-wait</option>.
-          </para>
-
-         </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--no-wait</option></term>
-        <listitem>
-          <para>
-            Don't wait to confirm that &repmgrd;
-            started successfully.
-          </para>
-          <para>
-            This is equivalent to providing <option>--wait=0</option>.
-          </para>
-         </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1 id="repmgr-daemon-start-configuration" xreflabel="repmgr daemon start configuration">
-    <title>Configuration file settings</title>
-    <para>
-     The following parameter in <filename>repmgr.conf</filename> is relevant
-     to <command>repmgr daemon start</command>:
-    </para>
-
-    <variablelist>
-
-      <varlistentry>
-
-        <term><option>repmgrd_service_start_command</option></term>
-        <listitem>
-          <indexterm>
-            <primary>repmgrd_service_start_command</primary>
-            <secondary>with &quot;repmgr daemon start&quot;</secondary>
-          </indexterm>
-
-          <para>
-            <command>repmgr daemon start</command> will execute the command defined by the
-            <varname>repmgrd_service_start_command</varname> parameter in <filename>repmgr.conf</filename>.
-            This must be set to a shell command which will start &repmgrd;;
-            if &repmgr; was installed from a package, this will be the service command defined by the
-            package. For more details see <link linkend="appendix-packages">Appendix: &repmgr; package details</link>.
-          </para>
-          <important>
-            <para>
-              If &repmgr; was installed from a system package, and you do not configure
-              <varname>repmgrd_service_start_command</varname> to an appropriate service command, this may
-              result in the system becoming confused about the state of the &repmgrd;
-              service; this is particularly the case with <literal>systemd</literal>.
-            </para>
-          </important>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-
-  </refsect1>
-
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr daemon start</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            The &repmgrd; start command (defined in
-            <varname>repmgrd_service_start_command</varname>) was successfully executed.
-          </para>
-          <para>
-            If the <option>--wait</option> option was provided, &repmgr; will confirm that
-            &repmgrd; has actually started up.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_BAD_CONFIG (1)</option></term>
-        <listitem>
-          <para>
-            <varname>repmgrd_service_start_command</varname> is not defined in
-            <filename>repmgr.conf</filename>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><option>ERR_DB_CONN (6)</option></term>
-        <listitem>
-          <para>
-            &repmgr; was unable to connect to the local PostgreSQL node.
-          </para>
-          <para>
-            PostgreSQL must be running before &repmgrd;
-            can be started. Additionally, unless the <option>--no-wait</option> option was
-            provided, &repmgr; needs to be able to connect to the local PostgreSQL node
-            to determine the state of &repmgrd;.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><option>ERR_REPMGRD_SERVICE (27)</option></term>
-        <listitem>
-          <para>
-            The &repmgrd; start command (defined in
-            <varname>repmgrd_service_start_command</varname>) was not successfully executed.
-          </para>
-          <para>
-            This can also mean that &repmgr; was unable to confirm whether &repmgrd;
-            successfully started (unless the <option>--no-wait</option> option was provided).
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-      <xref linkend="repmgr-daemon-stop"/>,
-      <xref linkend="repmgrd-daemon"/>,
-      <xref linkend="repmgr-service-status"/>,
-      <xref linkend="repmgr-service-pause"/>,
-      <xref linkend="repmgr-service-unpause"/>
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr-daemon-stop.xml

@@ -1,205 +0,0 @@
-<refentry id="repmgr-daemon-stop">
-  <indexterm>
-    <primary>repmgr daemon stop</primary>
-  </indexterm>
-
-  <indexterm>
-    <primary>repmgrd</primary>
-    <secondary>stopping</secondary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr daemon stop</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr daemon stop</refname>
-    <refpurpose>Stop the &repmgrd; daemon on the local node</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      This command stops the &repmgrd; daemon on the
-      local node.
-    </para>
-
-    <para>
-      By default, &repmgr; will wait for up to 15 seconds to confirm that &repmgrd;
-      stopped. This behaviour can be overridden by specifying a different value using the <option>--wait</option>
-      option, or disabled altogether with the <option>--no-wait</option> option.
-    </para>
-    <note>
-      <para>
-        If PostgreSQL is not running on the local node, under some circumstances &repmgr; may not
-        be able to confirm if &repmgrd; has actually stopped.
-      </para>
-    </note>
-
-   <important>
-      <para>
-        The <filename>repmgr.conf</filename> parameter <varname>repmgrd_service_stop_command</varname>
-        must be set for <command>repmgr daemon stop</command> to work; see section
-        <xref linkend="repmgr-daemon-stop-configuration"/> for details.
-      </para>
-    </important>
-  </refsect1>
-
-  <refsect1>
-    <title>Configuration</title>
-    <para>
-      <command>repmgr daemon stop</command> will execute the command defined by the
-      <varname>repmgrd_service_stop_command</varname> parameter in <filename>repmgr.conf</filename>.
-      This must be set to a shell command which will stop &repmgrd;;
-      if &repmgr; was installed from a package, this will be the service command defined by the
-      package. For more details see <link linkend="appendix-packages">Appendix: &repmgr; package details</link>.
-    </para>
-
-    <important>
-      <para>
-        If &repmgr; was installed from a system package, and you do not configure
-        <varname>repmgrd_service_stop_command</varname> to an appropriate service command, this may
-        result in the system becoming confused about the state of the &repmgrd;
-        service; this is particularly the case with <literal>systemd</literal>.
-      </para>
-    </important>
-
-  </refsect1>
-
-  <refsect1>
-
-    <title>Options</title>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually attempt to stop &repmgrd;.
-          </para>
-          <para>
-            This action will output the command which would be executed.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>-w</option></term>
-        <term><option>--wait</option></term>
-        <listitem>
-          <para>
-            Wait for the specified number of seconds to confirm that &repmgrd;
-            stopped successfully.
-          </para>
-          <para>
-            Note that providing <option>--wait=0</option> is the equivalent of <option>--no-wait</option>.
-          </para>
-
-         </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--no-wait</option></term>
-        <listitem>
-          <para>
-            Don't wait to confirm that &repmgrd;
-            stopped successfully.
-          </para>
-          <para>
-            This is equivalent to providing <option>--wait=0</option>.
-          </para>
-         </listitem>
-      </varlistentry>
-    </variablelist>
-  </refsect1>
-
-  <refsect1 id="repmgr-daemon-stop-configuration" xreflabel="repmgr daemon stop configuration">
-    <title>Configuration file settings</title>
-    <para>
-     The following parameter in <filename>repmgr.conf</filename> is relevant
-     to <command>repmgr daemon stop</command>:
-    </para>
-
-    <variablelist>
-
-      <varlistentry>
-
-        <term><option>repmgrd_service_stop_command</option></term>
-        <listitem>
-          <indexterm>
-            <primary>repmgrd_service_stop_command</primary>
-          <secondary>with &quot;repmgr daemon stop&quot;</secondary>
-          </indexterm>
-
-          <para>
-            <command>repmgr daemon stop</command> will execute the command defined by the
-            <varname>repmgrd_service_stop_command</varname> parameter in <filename>repmgr.conf</filename>.
-            This must be set to a shell command which will stop &repmgrd;;
-            if &repmgr; was installed from a package, this will be the service command defined by the
-            package. For more details see <link linkend="appendix-packages">Appendix: &repmgr; package details</link>.
-          </para>
-          <important>
-            <para>
-              If &repmgr; was installed from a system package, and you do not configure
-              <varname>repmgrd_service_stop_command</varname> to an appropriate service command, this may
-              result in the system becoming confused about the state of the &repmgrd;
-              service; this is particularly the case with <literal>systemd</literal>.
-            </para>
-          </important>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr daemon stop</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            &repmgrd; could be stopped.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_BAD_CONFIG (1)</option></term>
-        <listitem>
-          <para>
-            <varname>repmgrd_service_stop_command</varname> is not defined in
-            <filename>repmgr.conf</filename>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_REPMGRD_SERVICE (27)</option></term>
-        <listitem>
-          <para>
-            &repmgrd; could not be stopped.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-      <xref linkend="repmgr-daemon-start"/>,
-      <xref linkend="repmgrd-daemon"/>,
-      <xref linkend="repmgr-service-status"/>,
-      <xref linkend="repmgr-service-pause"/>,
-      <xref linkend="repmgr-service-unpause"/>
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr-node-check.xml

@@ -1,308 +0,0 @@
-<refentry id="repmgr-node-check">
-  <indexterm>
-    <primary>repmgr node check</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr node check</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr node check</refname>
-    <refpurpose>performs some health checks on a node from a replication perspective</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      Performs some health checks on a node from a replication perspective.
-      This command must be run on the local node.
-    </para>
-	<note>
-	  <para>
-		Currently &repmgr; performs health checks on physical replication
-		slots only, with the aim of warning about streaming replication standbys which
-		have become detached and the associated risk of uncontrolled WAL file
-		growth.
-	  </para>
-	</note>
-  </refsect1>
-
-  <refsect1>
-    <title>Example</title>
-    <para>
-      Execution on the primary server:
-      <programlisting>
-       $ repmgr -f /etc/repmgr.conf node check
-       Node "node1":
-            Server role: OK (node is primary)
-            Replication lag: OK (N/A - node is primary)
-            WAL archiving: OK (0 pending files)
-            Upstream connection: OK (N/A - is primary)
-            Downstream servers: OK (2 of 2 downstream nodes attached)
-            Replication slots: OK (node has no physical replication slots)
-            Missing replication slots: OK (node has no missing physical replication slots)
-            Configured data directory: OK (configured "data_directory" is "/var/lib/postgresql/data")</programlisting>
-    </para>
-    <para>
-      Execution on a standby server:
-      <programlisting>
-       $ repmgr -f /etc/repmgr.conf node check
-       Node "node2":
-            Server role: OK (node is standby)
-            Replication lag: OK (0 seconds)
-            WAL archiving: OK (0 pending archive ready files)
-            Upstream connection: OK (node "node2" (ID: 2) is attached to expected upstream node "node1" (ID: 1))
-            Downstream servers: OK (this node has no downstream nodes)
-            Replication slots: OK (node has no physical replication slots)
-            Missing physical replication slots: OK (node has no missing physical replication slots)
-            Configured data directory: OK (configured "data_directory" is "/var/lib/postgresql/data")</programlisting>
-    </para>
-  </refsect1>
-  <refsect1>
-    <title>Individual checks</title>
-    <para>
-      Each check can be performed individually by supplying
-      an additional command line parameter, e.g.:
-      <programlisting>
-        $ repmgr node check --role
-        OK (node is primary)</programlisting>
-    </para>
-    <para>
-	  Parameters for individual checks are as follows:
-    <itemizedlist spacing="compact" mark="bullet">
-
-     <listitem>
-      <simpara>
-        <option>--role</option>: checks if the node has the expected role
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        <option>--replication-lag</option>: checks if the node is lagging by more than
-        <varname>replication_lag_warning</varname> or <varname>replication_lag_critical</varname>
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        <option>--archive-ready</option>: checks for WAL files which have not yet been archived,
-        and returns <literal>WARNING</literal> or <literal>CRITICAL</literal> if the number
-        exceeds <varname>archive_ready_warning</varname> or <varname>archive_ready_critical</varname> respectively.
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        <option>--downstream</option>: checks that the expected downstream nodes are attached
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        <option>--upstream</option>: checks that the node is attached to its expected upstream
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        <option>--slots</option>: checks there are no inactive physical replication slots
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        <option>--missing-slots</option>: checks there are no missing physical replication slots
-      </simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>
-        <option>--data-directory-config</option>: checks the data directory configured in
-        <filename>repmgr.conf</filename> matches the actual data directory.
-        This check is not directly related to replication, but is useful to verify &repmgr;
-        is correctly configured.
-      </simpara>
-     </listitem>
-    </itemizedlist>
-  </para>
-  </refsect1>
-
-
-  <refsect1>
-    <title>repmgrd</title>
-    <para>
-      A separate check is available to verify whether &repmgrd; is running,
-      This is not included in the general output, as this does not
-      per-se constitute a check of the node's replication status.
-    </para>
-    <itemizedlist spacing="compact" mark="bullet">
-     <listitem>
-      <simpara>
-        <option>--repmgrd</option>: checks whether &repmgrd; is running.
-        If &repmgrd; is running but paused, status <literal>1</literal>
-        (<literal>WARNING</literal>) is returned.
-      </simpara>
-     </listitem>
-    </itemizedlist>
-  </refsect1>
-
-  <refsect1>
-    <title>Additional checks</title>
-    <para>
-      Several checks are provided for diagnostic purposes and are not
-      included in the general output:
-      <itemizedlist spacing="compact" mark="bullet">
-
-        <listitem>
-          <simpara>
-            <option>--db-connection</option>: checks if &repmgr; can connect to the
-            database on the local node.
-          </simpara>
-          <simpara>
-            This option is particularly useful in combination with <command>SSH</command>, as
-            it can be used to troubleshoot connection issues encountered when &repmgr; is
-            executed remotely (e.g. during a switchover operation).
-          </simpara>
-
-        </listitem>
-
-        <listitem>
-          <simpara>
-            <option>--replication-config-owner</option>: checks if the file containing replication
-            configuration (PostgreSQL 12 and later: <filename>postgresql.auto.conf</filename>;
-            PostgreSQL 11 and earlier: <filename>recovery.conf</filename>) is
-            owned by the same user who owns the data directory.
-          </simpara>
-          <simpara>
-            Incorrect ownership of these files (e.g. if they are owned by <literal>root</literal>)
-            will cause operations which need to update the replication configuration
-            (e.g. <link linkend="repmgr-standby-follow"><command>repmgr standby follow</command></link>
-            or <link linkend="repmgr-standby-promote"><command>repmgr standby promote</command></link>)
-            to fail.
-          </simpara>
-        </listitem>
-
-      </itemizedlist>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Connection options</title>
-    <para>
-      <itemizedlist spacing="compact" mark="bullet">
-
-        <listitem>
-          <simpara>
-            <option>-S</option>/<option>--superuser</option>: connect as the
-            named superuser instead of the &repmgr; user
-          </simpara>
-        </listitem>
-
-      </itemizedlist>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Output format</title>
-    <para>
-      <itemizedlist spacing="compact" mark="bullet">
-
-        <listitem>
-          <simpara>
-            <option>--csv</option>: generate output in CSV format (not available
-            for individual checks)
-          </simpara>
-        </listitem>
-
-        <listitem>
-          <simpara>
-            <option>--nagios</option>: generate output in a Nagios-compatible format
-            (for individual checks only)
-          </simpara>
-        </listitem>
-      </itemizedlist>
-    </para>
-  </refsect1>
-
-
-
-  <refsect1>
-    <title>Exit codes</title>
-
-    <para>
-      When executing <command>repmgr node check</command> with one of the individual
-      checks listed above, &repmgr; will emit one of the following Nagios-style exit codes
-      (even if <option>--nagios</option> is not supplied):
-
-      <itemizedlist spacing="compact" mark="bullet">
-
-        <listitem>
-          <simpara>
-            <literal>0</literal>: OK
-          </simpara>
-        </listitem>
-
-        <listitem>
-          <simpara>
-            <literal>1</literal>: WARNING
-          </simpara>
-        </listitem>
-
-        <listitem>
-          <simpara>
-            <literal>2</literal>: ERROR
-          </simpara>
-        </listitem>
-
-        <listitem>
-          <simpara>
-            <literal>3</literal>: UNKNOWN
-          </simpara>
-        </listitem>
-
-      </itemizedlist>
-    </para>
-
-
-
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr status check</command>
-      if no individual check was specified.
-    </para>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            No issues were detected.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_NODE_STATUS (25)</option></term>
-        <listitem>
-          <para>
-            One or more issues were detected.
-          </para>
-        </listitem>
-      </varlistentry>
-
-   </variablelist>
-
-  </refsect1>
-
-
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-     <xref linkend="repmgr-node-status"/>, <xref linkend="repmgr-cluster-show"/>
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr-node-rejoin.xml

@@ -1,505 +0,0 @@
-<refentry id="repmgr-node-rejoin">
-
-  <indexterm>
-    <primary>repmgr node rejoin</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr node rejoin</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr node rejoin</refname>
-    <refpurpose>rejoin a dormant (stopped) node to the replication cluster</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      Enables a dormant (stopped) node to be rejoined to the replication cluster.
-    </para>
-    <para>
-      This can optionally use <application>pg_rewind</application> to re-integrate
-      a node which has diverged from the rest of the cluster, typically a failed primary.
-    </para>
-    <para>
-      Note that <command>repmgr node rejoin</command> can only be used to attach
-      a standby to the current primary, not another standby.
-    </para>
-
-    <tip>
-      <para>
-        If the node is running and needs to be attached to the current primary, use
-        <xref linkend="repmgr-standby-follow"/>.
-      </para>
-      <para>
-        Note <xref linkend="repmgr-standby-follow"/> can only be used for standbys which have not diverged
-        from the rest of the cluster.
-      </para>
-    </tip>
-  </refsect1>
-
-
-  <refsect1>
-    <title>Usage</title>
-
-    <para>
-      <programlisting>
-      repmgr node rejoin -d '$conninfo'</programlisting>
-
-      where <literal>$conninfo</literal> is the PostgreSQL <literal>conninfo</literal> string of the
-      <emphasis>current</emphasis> primary node (or that of any reachable node in the cluster, but
-      <emphasis>not</emphasis> the local node). This is so that &repmgr; can fetch up-to-date information
-      about the current state of the cluster.
-    </para>
-    <para>
-      <filename>repmgr.conf</filename> for the stopped node *must* be supplied explicitly if not
-      otherwise available.
-    </para>
-  </refsect1>
-
-  <refsect1>
-
-    <title>Options</title>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually execute the rejoin.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--force-rewind</option></term>
-        <listitem>
-          <para>
-            Execute <application>pg_rewind</application>.
-          </para>
-          <para>
-            See <xref linkend="repmgr-node-rejoin-pg-rewind"/> for more details on using
-            <application>pg_rewind</application>.
-          </para>
-
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--config-files</option></term>
-        <listitem>
-          <para>
-            comma-separated list of configuration files to retain after
-            executing <application>pg_rewind</application>.
-          </para>
-          <para>
-            Currently <application>pg_rewind</application> will overwrite
-            the local node's configuration files with the files from the source node,
-            so it's advisable to use this option to ensure they are kept.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><option>--config-archive-dir</option></term>
-        <listitem>
-          <para>
-            Directory to temporarily store configuration files specified with
-            <option>--config-files</option>; default: <filename>/tmp</filename>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><option>-W/--no-wait</option></term>
-        <listitem>
-          <para>
-            Don't wait for the node to rejoin cluster.
-          </para>
-          <para>
-            If this option is supplied, &repmgr; will restart the node but
-            not wait for it to connect to the primary.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>Configuration file settings</title>
-
-    <para>
-      <itemizedlist spacing="compact" mark="bullet">
-       <listitem>
-         <simpara>
-           <literal>node_rejoin_timeout</literal>:
-		   the maximum length of time (in seconds) to wait for
-		   the node to reconnect to the replication cluster (defaults to
-		   the value set in <literal>standby_reconnect_timeout</literal>,
-		   60 seconds).
-		 </simpara>
-         <simpara>
-           Note that <literal>standby_reconnect_timeout</literal> must be
-           set to a value equal to or greater than
-           <literal>node_rejoin_timeout</literal>.
-         </simpara>
-	   </listitem>
-	  </itemizedlist>
-	</para>
-
-  </refsect1>
-
-  <refsect1 id="repmgr-node-rejoin-events">
-    <title>Event notifications</title>
-    <para>
-      A <literal>node_rejoin</literal> <link linkend="event-notifications">event notification</link> will be generated.
-    </para>
-  </refsect1>
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr node rejoin</command>:
-    </para>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            The node rejoin succeeded; or if <option>--dry-run</option> was provided,
-            no issues were detected which would prevent the node rejoin.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_BAD_CONFIG (1)</option></term>
-        <listitem>
-          <para>
-            A configuration issue was detected which prevented &repmgr; from
-            continuing with the node rejoin.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_NO_RESTART (4)</option></term>
-        <listitem>
-          <para>
-            The node could not be restarted.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_REJOIN_FAIL (24)</option></term>
-        <listitem>
-          <para>
-            The node rejoin operation failed.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Notes</title>
-    <para>
-      Currently <command>repmgr node rejoin</command> can only be used to attach
-      a standby to the current primary, not another standby.
-    </para>
-    <para>
-      The node's PostgreSQL instance  must have been shut down cleanly. If this was not the
-      case, it will need to be started up until it has reached a consistent recovery point,
-      then shut down cleanly.
-    </para>
-    <para>
-      In PostgreSQL 13 and later, this will be done automatically
-      if the <option>--force-rewind</option> is provided (even if an actual rewind
-      is not necessary).
-    </para>
-    <para>
-      With PostgreSQL 12 and earlier, PostgreSQL will need to
-      be started and shut down manually; see below for the best way to do this.
-    </para>
-    <tip>
-      <para>
-        If <application>PostgreSQL</application> is started in single-user mode and
-        input is directed from <filename>/dev/null/</filename>, it will perform recovery
-        then immediately quit, and will then be in a state suitable for use by
-        <application>pg_rewind</application>.
-        <programlisting>
-          rm -f /var/lib/pgsql/data/recovery.conf
-          postgres --single -D /var/lib/pgsql/data/ &lt; /dev/null</programlisting>
-      </para>
-      <para>
-        Note that  <filename>standby.signal</filename> (PostgreSQL 11 and earlier:
-        <filename>recovery.conf</filename>) <emphasis>must</emphasis> be removed
-        from the data directory for PostgreSQL to be able to start in single
-        user mode.
-      </para>
-    </tip>
-
-  </refsect1>
-
-  <refsect1 id="repmgr-node-rejoin-pg-rewind" xreflabel="Using pg_rewind">
-
-   <title>Using <command>pg_rewind</command></title>
-
-   <indexterm>
-      <primary>pg_rewind</primary>
-      <secondary>using with "repmgr node rejoin"</secondary>
-    </indexterm>
-
-    <para>
-      <command>repmgr node rejoin</command> can optionally use <command>pg_rewind</command> to re-integrate a
-      node which has diverged from the rest of the cluster, typically a failed primary.
-    </para>
-    <note>
-      <para>
-        <command>pg_rewind</command> <emphasis>requires</emphasis> that either
-        <varname>wal_log_hints</varname> is enabled, or that
-        data checksums were enabled when the cluster was initialized. See the
-        <ulink url="https://www.postgresql.org/docs/current/app-pgrewind.html"><command>pg_rewind</command> documentation</ulink> for details.
-      </para>
-      <para>
-        Additionally, <varname>full_page_writes</varname> must be enabled; this is the default and
-        normally should never be disabled.
-      </para>
-    </note>
-
-    <para>
-      We strongly recommend familiarizing yourself with <command>pg_rewind</command> before attempting
-      to use it with &repmgr;, as while it is an extremely useful tool, it is <emphasis>not</emphasis>
-      a &quot;magic bullet&quot; which can resolve all problematic replication situations.
-    </para>
-
-    <para>
-      A typical use-case for <command>pg_rewind</command> is when a scenario like the following
-      is encountered:
-      <programlisting>
-    $ repmgr node rejoin -f /etc/repmgr.conf -d 'host=node3 dbname=repmgr user=repmgr' \
-        --force-rewind --config-files=postgresql.local.conf,postgresql.conf --verbose --dry-run
-    NOTICE: rejoin target is node "node3" (node ID: 3)
-    INFO: replication connection to the rejoin target node was successful
-    INFO: local and rejoin target system identifiers match
-    DETAIL: system identifier is 6652184002263212600
-    ERROR: this node cannot attach to rejoin target node 3
-    DETAIL: rejoin target server's timeline 2 forked off current database system timeline 1 before current recovery point 0/610D710
-    HINT: use --force-rewind to execute pg_rewind</programlisting>
-
-      Here, <literal>node3</literal> was promoted to a primary while the local node was
-      still attached to the previous primary; this can potentially happen during e.g. a
-      network split. <command>pg_rewind</command> can re-sync the local node with <literal>node3</literal>,
-      removing the need for a full reclone.
-    </para>
-
-    <para>
-      To have <command>repmgr node rejoin</command> use <command>pg_rewind</command>,
-      pass the command line option <literal>--force-rewind</literal>, which will tell &repmgr;
-      to execute <command>pg_rewind</command> to ensure the node can be rejoined successfully.
-    </para>
-
-    <refsect2 id="repmgr-node-rejoin-pg-rewind-config-files" xreflabel="pg_rewind and configuration files">
-
-      <title><command>pg_rewind</command> and configuration file retention</title>
-
-      <indexterm>
-        <primary>pg_rewind</primary>
-        <secondary>configuration file retention</secondary>
-      </indexterm>
-
-      <para>
-        Be aware that if <command>pg_rewind</command> is executed and actually performs a
-        rewind operation, any configuration files in the PostgreSQL data directory will be
-        overwritten with those from the source server.
-      </para>
-      <para>
-        To prevent this happening, provide a comma-separated list of files to retain
-        using the <option>--config-file</option> command line option; the specified files
-        will be archived in a temporary directory (whose parent directory can be specified with
-        <option>--config-archive-dir</option>, default: <filename>/tmp</filename>)
-        and restored once the rewind operation is complete.
-      </para>
-    </refsect2>
-
-    <refsect2 id="repmgr-node-rejoin-pg-rewind-example" xreflabel="example using repmgr node rejoin and pg_rewind">
-
-      <title>Example using <command>repmgr node rejoin</command> and <command>pg_rewind</command></title>
-
-      <indexterm>
-        <primary>pg_rewind</primary>
-        <secondary>configuration file retention</secondary>
-      </indexterm>
-
-
-      <para>
-        Example, first using <option>--dry-run</option>, then actually executing the
-        <literal>node rejoin command</literal>.
-        <programlisting>
-    $ repmgr node rejoin -f /etc/repmgr.conf -d 'host=node3 dbname=repmgr user=repmgr' \
-        --config-files=postgresql.local.conf,postgresql.conf --verbose --force-rewind --dry-run
-    NOTICE: rejoin target is node "node3" (node ID: 3)
-    INFO: replication connection to the rejoin target node was successful
-    INFO: local and rejoin target system identifiers match
-    DETAIL: system identifier is 6652460429293670710
-    NOTICE: pg_rewind execution required for this node to attach to rejoin target node 3
-    DETAIL: rejoin target server's timeline 2 forked off current database system timeline 1 before current recovery point 0/610D710
-    INFO: prerequisites for using pg_rewind are met
-    INFO: file "postgresql.local.conf" would be copied to "/tmp/repmgr-config-archive-node2/postgresql.local.conf"
-    INFO: file "postgresql.replication-setup.conf" would be copied to "/tmp/repmgr-config-archive-node2/postgresql.replication-setup.conf"
-    INFO: pg_rewind would now be executed
-    DETAIL: pg_rewind command is:
-      pg_rewind -D '/var/lib/postgresql/data' --source-server='host=node3 dbname=repmgr user=repmgr'
-    INFO: prerequisites for executing NODE REJOIN are met</programlisting>
-
-        <note>
-          <para>
-            If <option>--force-rewind</option> is used with the <option>--dry-run</option> option,
-            this checks the prerequisites for using <application>pg_rewind</application>, but is
-            not an absolute guarantee that actually executing <application>pg_rewind</application>
-            will succeed. See also section <xref linkend="repmgr-node-rejoin-caveats"/> below.
-          </para>
-
-        </note>
-
-        <programlisting>
-    $ repmgr node rejoin -f /etc/repmgr.conf -d 'host=node3 dbname=repmgr user=repmgr' \
-        --config-files=postgresql.local.conf,postgresql.conf --verbose --force-rewind
-    NOTICE: pg_rewind execution required for this node to attach to rejoin target node 3
-    DETAIL: rejoin target server's timeline 2 forked off current database system timeline 1 before current recovery point 0/610D710
-    NOTICE: executing pg_rewind
-    DETAIL: pg_rewind command is "pg_rewind -D '/var/lib/postgresql/data' --source-server='host=node3 dbname=repmgr user=repmgr'"
-    NOTICE: 2 files copied to /var/lib/postgresql/data
-    NOTICE: setting node 2's upstream to node 3
-    NOTICE: starting server using "pg_ctl -l /var/log/postgres/startup.log -w -D '/var/lib/pgsql/data' start"
-    NOTICE: NODE REJOIN successful
-    DETAIL: node 2 is now attached to node 3</programlisting>
-      </para>
-    </refsect2>
-
-    <refsect2 id="repmgr-node-rejoin-postgresql-94" xreflabel="pg_rewind and PostgreSQL 9.4">
-
-      <title><command>pg_rewind</command> and PostgreSQL 9.4</title>
-
-      <indexterm>
-        <primary>pg_rewind</primary>
-        <secondary>PostgreSQL 9.4</secondary>
-      </indexterm>
-
-      <para>
-        <application>pg_rewind</application> is available in PostgreSQL 9.5 and later as part of the core distribution.
-        Users of PostgreSQL 9.4 will need to manually install it; the source code is available here:
-        <ulink url="https://github.com/vmware/pg_rewind">https://github.com/vmware/pg_rewind</ulink>.
-        If the <application>pg_rewind</application>
-        binary is not installed in the PostgreSQL <filename>bin</filename> directory, provide
-        its full path  on the demotion candidate  with <option>--force-rewind</option>.
-      </para>
-      <para>
-        Note that building the 9.4 version of <application>pg_rewind</application> requires the PostgreSQL
-        source code.
-      </para>
-    </refsect2>
-  </refsect1>
-
-  <refsect1 id="repmgr-node-rejoin-caveats" xreflabel="Caveats">
-
-   <title>Caveats when using <command>repmgr node rejoin</command></title>
-
-   <indexterm>
-     <primary>repmgr node rejoin</primary>
-     <secondary>caveats</secondary>
-   </indexterm>
-
-   <para>
-     <command>repmgr node rejoin</command> attempts to determine whether it will succeed by
-     comparing the timelines and relative WAL positions of the local node (rejoin candidate) and primary
-     (rejoin target). This is particularly important if planning to use <application>pg_rewind</application>,
-     which currently (as of PostgreSQL 12) may appear to succeed (or indicate there is no action
-     needed) but potentially allow an impossible action, such as trying to rejoin a standby to a
-     primary which is behind the standby. &repmgr; will prevent this situation from occurring.
-   </para>
-   <para>
-     Currently it is <emphasis>not</emphasis> possible to detect a situation where the rejoin target
-     is a standby which has been &quot;promoted&quot; by removing <filename>recovery.conf</filename>
-     (PostgreSQL 12 and later: <filename>standby.signal</filename>) and restarting it.
-     In this case there will be no information about the point the rejoin target diverged
-     from the current standby; the rejoin operation will fail and
-     the current standby's PostgreSQL log will contain entries with the text
-     &quot;<literal>record with incorrect prev-link</literal>&quot;.
-   </para>
-   <para>
-     In PostgreSQL 9.5 and earlier, it is <emphasis>not</emphasis> possible to use
-     <application>pg_rewind</application> to attach to a target node with a lower
-     timeline than the local node.
-   </para>
-   <para>
-     We strongly recommend running <command>repmgr node rejoin</command> with the
-     <option>--dry-run</option> option first. Additionally it might be a good idea
-     to execute the <application>pg_rewind</application> command displayed by
-     &repmgr; with the <application>pg_rewind</application> <option>--dry-run</option>
-     option. Note that <application>pg_rewind</application> does not indicate that it
-     is running in <option>--dry-run</option> mode.
-   </para>
-
-   <warning>
-     <para>
-       In all PostgreSQL released before February 2021, <application>pg_rewind</application>
-       contains a corner-case bug which affects standbys in a very specific situation.
-     </para>
-     <para>
-       This situation occurs when a standby was shut down <emphasis>before</emphasis> its
-       primary node, and an attempt is made to attach this standby to another primary
-       in the same cluster (following a &quot;split brain&quot; situation where the standby
-       was connected to the wrong primary). In this case, &repmgr; will correctly determine
-       that <application>pg_rewind</application> should be executed, however
-       <application>pg_rewind</application> incorrectly decides that no action is necessary.
-     </para>
-     <para>
-       In this situation, &repmgr; will report something like:
-<programlisting>
-    NOTICE: pg_rewind execution required for this node to attach to rejoin target node 1
-    DETAIL: rejoin target server's timeline 3 forked off current database system timeline 2 before current recovery point 0/7019C10</programlisting>
-       but when executed, <application>pg_rewind</application> will report:
-<programlisting>
-    pg_rewind: servers diverged at WAL location 0/7015540 on timeline 2
-    pg_rewind: no rewind required</programlisting>
-       and if an attempt is made to attach the standby to the new primary, PostgreSQL logs on the standby
-       will contain errors like:
-<programlisting>
-    [2020-09-07 15:01:41 UTC]    LOG:  00000: replication terminated by primary server
-    [2020-09-07 15:01:41 UTC]    DETAIL:  End of WAL reached on timeline 2 at 0/7015540.
-    [2020-09-07 15:01:41 UTC]    LOG:  00000: new timeline 3 forked off current database system timeline 2 before current recovery point 0/7019C10</programlisting>
-     </para>
-     <para>
-       Currently it is not possible to resolve this situation using <application>pg_rewind</application>.
-       A <ulink url="https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=2b4f3130382fe2f8705863e4d38589d4d69cd695">patch</ulink>
-       was submitted and is included in all PostgreSQL versions released in February 2021 or later.
-     </para>
-     <para>
-       As a workaround, start the primary server the standby was previously attached to,
-       and ensure the standby can be attached to it. If <application>pg_rewind</application> was actually executed,
-       it will have copied in the <filename>.history</filename> file from the target primary server; this must
-       be removed. <command>repmgr node rejoin</command> can then be used to attach the standby to the original
-       primary. Ensure any changes pending on the primary have propagated to the standby. Then shut down the primary
-       server <emphasis>first</emphasis>, before shutting down the standby. It should then be possible to
-       use <command>repmgr node rejoin</command> to attach the standby to the new primary.
-     </para>
-   </warning>
-
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-     <xref linkend="repmgr-standby-follow"/>, <xref linkend="repmgr-standby-switchover"/>
-    </para>
-  </refsect1>
-</refentry>

doc/repmgr-node-service.xml

@@ -1,166 +0,0 @@
-<refentry id="repmgr-node-service">
-  <indexterm>
-    <primary>repmgr node service</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr node service</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr node service</refname>
-    <refpurpose>show or execute the system service command to stop/start/restart/reload/promote a node</refpurpose>
-  </refnamediv>
-
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      Shows or executes the system service command to stop/start/restart/reload a node.
-    </para>
-    <para>
-      This command is mainly meant for internal &repmgr; usage, but is useful for
-      confirming the command configuration.
-    </para>
-  </refsect1>
-
-  <refsect1>
-
-    <title>Options</title>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Log the steps which would be taken, including displaying the command which would be executed.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--action</option></term>
-        <listitem>
-          <para>
-            The action to perform. One of <literal>start</literal>, <literal>stop</literal>,
-            <literal>restart</literal>, <literal>reload</literal> or <literal>promote</literal>.
-          </para>
-          <para>
-            If the parameter <option>--list-actions</option> is provided together with
-            <option>--action</option>, the command which would be executed will be printed.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><option>--list-actions</option></term>
-        <listitem>
-          <para>
-            List all configured commands.
-          </para>
-          <para>
-            If the parameter <option>--action</option> is provided together with
-            <option>--list-actions</option>, the command which would be executed for that
-            particular action will be printed.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-     <varlistentry>
-        <term><option>--checkpoint</option></term>
-        <listitem>
-          <para>
-            Issue a <command>CHECKPOINT</command> before stopping or restarting the node.
-          </para>
-          <para>
-            Note that a superuser connection is required to be able to execute the
-            <command>CHECKPOINT</command> command. From PostgreSQL 15 the <varname>pg_checkpoint</varname>
-            predefined role removes the need for superuser permissions to perform <command>CHECKPOINT</command> command.
-          </para>
-        </listitem>
-     </varlistentry>
-
-     <varlistentry>
-        <term><option>-S</option>/<option>--superuser</option></term>
-        <listitem>
-          <para>
-           Connect as the named superuser instead of the normal &repmgr; user.
-          </para>
-        </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr node service</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            No issues were detected.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_LOCAL_COMMAND (5)</option></term>
-        <listitem>
-          <para>
-            Execution of the system service command failed.
-          </para>
-        </listitem>
-      </varlistentry>
-
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>Examples</title>
-    <para>
-      See what action would be taken for a restart:
-      <programlisting>
-[postgres@node1 ~]$ repmgr -f /etc/repmgr/12/repmgr.conf node service --action=restart --checkpoint --dry-run
-INFO: a CHECKPOINT would be issued here
-INFO: would execute server command "sudo service postgresql-12 restart"</programlisting>
-    </para>
-
-    <para>
-      Restart the PostgreSQL instance:
-      <programlisting>
-[postgres@node1 ~]$ repmgr -f /etc/repmgr/12/repmgr.conf node service --action=restart --checkpoint
-NOTICE: issuing CHECKPOINT
-DETAIL: executing server command "sudo service postgresql-12 restart"
-Redirecting to /bin/systemctl restart postgresql-12.service</programlisting>
-    </para>
-
-    <para>
-      List all commands:
-      <programlisting>
-[postgres@node1 ~]$ repmgr -f /etc/repmgr/12/repmgr.conf node service --list-actions
-Following commands would be executed for each action:
-
-    start: "sudo service postgresql-12 start"
-     stop: "sudo service postgresql-12 stop"
-  restart: "sudo service postgresql-12 restart"
-   reload: "sudo service postgresql-12 reload"
-  promote: "/usr/pgsql-12/bin/pg_ctl  -w -D '/var/lib/pgsql/12/data' promote"</programlisting>
-    </para>
-
-    <para>
-      List a single command:
-      <programlisting>
-[postgres@node1 ~]$ repmgr -f /etc/repmgr/12/repmgr.conf node service --list-actions --action=promote
-/usr/pgsql-12/bin/pg_ctl  -w -D '/var/lib/pgsql/12/data' promote      </programlisting>
-    </para>
-  </refsect1>
-</refentry>

doc/repmgr-node-status.xml

@@ -1,91 +0,0 @@
-<refentry id="repmgr-node-status">
-  <indexterm>
-    <primary>repmgr node status</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr node status</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr node status</refname>
-    <refpurpose>show overview of a node's basic information and replication status</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      Displays an overview of a node's basic information and replication
-      status. This command must be run on the local node.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Example</title>
-    <para>
-    <programlisting>
-        $ repmgr -f /etc/repmgr.conf node status
-        Node "node1":
-            PostgreSQL version: 10beta1
-            Total data size: 30 MB
-            Conninfo: host=node1 dbname=repmgr user=repmgr connect_timeout=2
-            Role: primary
-            WAL archiving: off
-            Archive command: (none)
-            Replication connections: 2 (of maximal 10)
-            Replication slots: 0 (of maximal 10)
-            Replication lag: n/a</programlisting>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Output format</title>
-    <para>
-      <itemizedlist spacing="compact" mark="bullet">
-
-        <listitem>
-          <simpara>
-            <literal>--csv</literal>: generate output in CSV format
-          </simpara>
-        </listitem>
-      </itemizedlist>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr node status</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            No issues were detected.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_NODE_STATUS (25)</option></term>
-        <listitem>
-          <para>
-            One or more issues were detected.
-          </para>
-        </listitem>
-      </varlistentry>
-
-   </variablelist>
-  </refsect1>
-
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-      See <xref linkend="repmgr-node-check"/> to diagnose issues and <xref linkend="repmgr-cluster-show"/>
-      for an overview of all nodes in the cluster.
-    </para>
-  </refsect1>
-</refentry>

doc/repmgr-primary-register.xml

@@ -1,124 +0,0 @@
-<refentry id="repmgr-primary-register">
-  <indexterm>
-    <primary>repmgr primary register</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr primary register</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr primary register</refname>
-    <refpurpose>initialise a repmgr installation and register the primary node</refpurpose>
-  </refnamediv>
-
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      <command>repmgr primary register</command> registers a primary node in a
-      streaming replication cluster, and configures it for use with &repmgr;, including
-      installing the &repmgr; extension. This command needs to be executed before any
-      standby nodes are registered.
-    </para>
-
-    <note>
-      <para>
-        &repmgr; will attempt to install the &repmgr; extension as part of this command,
-        however this will fail if the <literal>repmgr</literal> user is not a superuser.
-      </para>
-      <para>
-        It's possible to install the &repmgr; extension manually before executing
-        <command>repmgr primary register</command>; in this case &repmgr; will
-        detect the presence of the extension and skip that step.
-      </para>
- 
-    </note>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Execution</title>
-    <para>
-      Execute with the <option>--dry-run</option> option to check what would happen without
-      actually registering the primary.
-    </para>
-
-    <note>
-      <para>
-        If providing the configuration file location with <option>-f/--config-file</option>,
-        avoid using a relative path, as &repmgr; stores the configuration file location
-        in the repmgr metadata for use when &repmgr; is executed remotely (e.g. during
-        <xref linkend="repmgr-standby-switchover"/>). &repmgr; will attempt to convert the
-          a relative path into an absolute one, but this may not be the same as the path you
-          would explicitly provide (e.g. <filename>./repmgr.conf</filename> might be converted
-          to <filename>/path/to/./repmgr.conf</filename>, whereas you'd normally write
-          <filename>/path/to/repmgr.conf</filename>).
-      </para>
-    </note>
-
-	<para>
-      <command>repmgr master register</command> can be used as an alias for
-      <command>repmgr primary register</command>.
-    </para>
-
-  </refsect1>
-
-  <refsect1>
-    <title>User permission requirements</title>
-    <para>
-      The <literal>repmgr</literal> user must be a superuser in order for &repmgr;
-      to be able to install the <literal>repmgr</literal> extension.
-    </para>
-    <para>
-      If this is not the case, the <literal>repmgr</literal> extension can be installed
-      manually before executing <command>repmgr primary register</command>.
-    </para>
-    <para>
-      A future &repmgr; release will enable the provision of a <option>--superuser</option>
-      name for the installation of the extension.
-    </para>
-  </refsect1>
-  <refsect1>
-
-    <title>Options</title>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually register the primary.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>-F</option>, <option>--force</option></term>
-        <listitem>
-          <para>
-            Overwrite an existing node record
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-
-  <refsect1 id="repmgr-primary-register-events">
-    <title>Event notifications</title>
-    <para>
-      Following <link linkend="event-notifications">event notifications</link> will be generated:
-      <itemizedlist spacing="compact" mark="bullet">
-        <listitem>
-          <simpara><literal>cluster_created</literal></simpara>
-        </listitem>
-        <listitem>
-          <simpara><literal>primary_register</literal></simpara>
-        </listitem>
-      </itemizedlist>
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr-primary-unregister.xml

@@ -1,85 +0,0 @@
-<refentry id="repmgr-primary-unregister">
-  <indexterm>
-    <primary>repmgr primary unregister</primary>
-  </indexterm>
-  <refmeta>
-    <refentrytitle>repmgr primary unregister</refentrytitle>
-  </refmeta>
-  <refnamediv>
-    <refname>repmgr primary unregister</refname>
-    <refpurpose>unregister an inactive primary node</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      <command>repmgr primary unregister</command> unregisters an inactive primary node
-      from the &repmgr; metadata. This is typically when the primary has failed and is
-      being removed from the cluster after a new primary has been promoted.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Execution</title>
-    <para>
-      <command>repmgr primary unregister</command> can be run on any active &repmgr; node,
-      with the ID of the node to unregister passed as <option>--node-id</option>.
-    </para>
-    <para>
-      Execute with the <literal>--dry-run</literal> option to check what would happen without
-      actually unregistering the node.
-    </para>
-
-    <para>
-      <command>repmgr master unregister</command> can be used as an alias for
-      <command>repmgr primary unregister</command>.
-    </para>
-  </refsect1>
-
-  <refsect1>
-
-    <title>Options</title>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually unregister the primary.
-          </para>
-        </listitem>
-      </varlistentry>
-
-     <varlistentry>
-        <term><option>--node-id</option></term>
-        <listitem>
-          <para>
-            ID of the inactive primary to be unregistered.
-          </para>
-        </listitem>
-      </varlistentry>
-
-     <varlistentry>
-        <term><option>--force</option></term>
-        <listitem>
-          <para>
-            Forcibly unregister the node if it is registered as an active primary,
-            as long as it has no registered standbys; or if it is registered as
-            a primary but running as a standby.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </refsect1>
-
-  <refsect1 id="repmgr-primary-unregister-events">
-    <title>Event notifications</title>
-    <para>
-      A <literal>primary_unregister</literal> <link linkend="event-notifications">event notification</link> will be generated.
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr-service-pause.xml

@@ -1,127 +0,0 @@
-<refentry id="repmgr-service-pause">
-  <indexterm>
-    <primary>repmgr service pause</primary>
-  </indexterm>
-
-  <indexterm>
-    <primary>repmgrd</primary>
-    <secondary>pausing</secondary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr service pause</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr service pause</refname>
-    <refpurpose>Instruct all &repmgrd; instances in the replication cluster to pause failover operations</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      This command can be run on any active node in the replication cluster to instruct all
-      running &repmgrd; instances to &quot;pause&quot; themselves, i.e. take no
-      action (such as promoting themselves or following a new primary) if a failover event is detected.
-    </para>
-    <para>
-      This functionality is useful for performing maintenance operations, such as switchovers
-      or upgrades, which might otherwise trigger a failover if &repmgrd;
-      is running normally.
-    </para>
-    <note>
-      <para>
-        It's important to wait a few seconds after restarting PostgreSQL on any node before running
-        <command>repmgr service pause</command>, as the &repmgrd; instance
-        on the restarted node will take a second or two before it has updated its status.
-      </para>
-    </note>
-    <para>
-      <xref linkend="repmgr-service-unpause"/> will instruct all previously paused &repmgrd;
-      instances to resume normal failover operation.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Prerequisites</title>
-    <para>
-      PostgreSQL must be accessible on all nodes (using the <varname>conninfo</varname> string shown by
-      <link linkend="repmgr-cluster-show"><command>repmgr cluster show</command></link>)
-      from the node where <command>repmgr service pause</command> is executed.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Execution</title>
-    <para>
-      <command>repmgr service pause</command> can be executed on any active node in the
-      replication cluster. A valid <filename>repmgr.conf</filename> file is required.
-      It will have no effect on previously paused nodes.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Example</title>
-    <para>
-    <programlisting>
-$ repmgr -f /etc/repmgr.conf service pause
-NOTICE: node 1 (node1) paused
-NOTICE: node 2 (node2) paused
-NOTICE: node 3 (node3) paused</programlisting>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Options</title>
-    <variablelist>
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check if nodes are reachable but don't pause &repmgrd;.
-          </para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr service unpause</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            &repmgrd; could be paused on all nodes.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_REPMGRD_PAUSE (26)</option></term>
-        <listitem>
-          <para>
-           &repmgrd; could not be paused on one or mode nodes.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-      <xref linkend="repmgr-service-unpause"/>,
-      <xref linkend="repmgr-service-status"/>,
-      <xref linkend="repmgrd-pausing"/>,
-      <xref linkend="repmgr-daemon-start"/>,
-      <xref linkend="repmgr-daemon-stop"/>
-    </para>
-  </refsect1>
-</refentry>
-

doc/repmgr-service-status.xml

@@ -1,215 +0,0 @@
-<refentry id="repmgr-service-status">
-  <indexterm>
-    <primary>repmgr service status</primary>
-  </indexterm>
-
-  <indexterm>
-    <primary>repmgrd</primary>
-    <secondary>displaying service status</secondary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr service status</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr service status</refname>
-    <refpurpose>display information about the status of &repmgrd; on each node in the cluster</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      This command provides an overview over all active nodes in the cluster and the state
-      of each node's &repmgrd; instance. It can be used to check
-      the result of <xref linkend="repmgr-service-pause"/> and <xref linkend="repmgr-service-unpause"/>
-      operations.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Prerequisites</title>
-    <para>
-      PostgreSQL should be accessible on all nodes (using the <varname>conninfo</varname> string shown by
-      <link linkend="repmgr-cluster-show"><command>repmgr cluster show</command></link>)
-      from the node where <command>repmgr service status</command> is executed.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Execution</title>
-    <para>
-      <command>repmgr service status</command> can be executed on any active node in the
-      replication cluster. A valid <filename>repmgr.conf</filename> file is required.
-    </para>
-    <para>
-      If a node is not accessible, or PostgreSQL itself is not running on the node,
-      &repmgr; will not be able to determine the status of that node's &repmgrd; instance,
-      and &quot;<literal>n/a</literal>&quot; will be displayed in the node's <literal>repmgrd</literal>
-      column.
-    </para>
-
-    <note>
-      <para>
-        After restarting PostgreSQL on any node, the &repmgrd; instance
-        will take a second or two before it is able to update its status. Until then,
-        &repmgrd; will be shown as not running.
-      </para>
-    </note>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Examples</title>
-    <para>
-      &repmgrd; running normally on all nodes:
-    <programlisting>$ repmgr -f /etc/repmgr.conf service status
- ID | Name  | Role    | Status    | Upstream | repmgrd | PID   | Paused? | Upstream last seen
-----+-------+---------+-----------+----------+---------+-------+---------+--------------------
- 1  | node1 | primary | * running |          | running | 96563 | no      | n/a
- 2  | node2 | standby |   running | node1    | running | 96572 | no      | 1 second(s) ago
- 3  | node3 | standby |   running | node1    | running | 96584 | no      | 0 second(s) ago</programlisting>
-    </para>
-
-    <para>
-      &repmgrd; paused on all nodes (using <xref linkend="repmgr-service-pause"/>):
-    <programlisting>$ repmgr -f /etc/repmgr.conf service status
- ID | Name  | Role    | Status    | Upstream | repmgrd | PID   | Paused? | Upstream last seen
-----+-------+---------+-----------+----------+---------+-------+---------+--------------------
- 1  | node1 | primary | * running |          | running | 96563 | yes     | n/a
- 2  | node2 | standby |   running | node1    | running | 96572 | yes     | 1 second(s) ago
- 3  | node3 | standby |   running | node1    | running | 96584 | yes     | 0 second(s) ago</programlisting>
-    </para>
-
-    <para>
-      &repmgrd; not running on one node:
-    <programlisting>$ repmgr -f /etc/repmgr.conf service status
- ID | Name  | Role    | Status    | Upstream | repmgrd     | PID   | Paused? | Upstream last seen
-----+-------+---------+-----------+----------+-------------+-------+---------+--------------------
- 1  | node1 | primary | * running |          | running     | 96563 | yes     | n/a
- 2  | node2 | standby |   running | node1    | not running | n/a   | n/a     | n/a
- 3  | node3 | standby |   running | node1    | running     | 96584 | yes     | 0 second(s) ago</programlisting>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Options</title>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--csv</option></term>
-        <listitem>
-          <para>
-            <command>repmgr service status</command> accepts an optional parameter <literal>--csv</literal>, which
-            outputs the replication cluster's status in a simple CSV format, suitable for
-            parsing by scripts, e.g.:
-            <programlisting>
-    $ repmgr -f /etc/repmgr.conf service status --csv
-    1,node1,primary,1,1,5722,1,100,-1,default
-    2,node2,standby,1,0,-1,1,100,1,default
-    3,node3,standby,1,1,5779,1,100,1,default</programlisting>
-          </para>
-          <para>
-            The columns have following meanings:
-            <itemizedlist spacing="compact" mark="bullet">
-              <listitem>
-                <simpara>
-                  node ID
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  node name
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  node type (primary or standby)
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  PostgreSQL server running (1 = running, 0 = not running)
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  &repmgrd; running (1 = running, 0 = not running, -1 = unknown)
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  &repmgrd; PID (-1 if not running or status unknown)
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  &repmgrd; paused (1 = paused, 0 = not paused, -1 = unknown)
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  &repmgrd; node priority
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  interval in seconds since the node's upstream was last seen (this will be -1 if the value could not be retrieved, or the node is primary)
-                </simpara>
-              </listitem>
-
-			  <listitem>
-                <simpara>
-                  node location
-                </simpara>
-              </listitem>
-
-            </itemizedlist>
-          </para>
-        </listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-        <term><option>--detail</option></term>
-        <listitem>
-          <para>
-            Display additional information (<literal>location</literal>, <literal>priority</literal>)
-	    about the &repmgr; configuration.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--verbose</option></term>
-        <listitem>
-          <para>
-            Display the full text of any database connection error messages.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-      <xref linkend="repmgr-service-pause"/>,
-      <xref linkend="repmgr-service-unpause"/>,
-      <xref linkend="repmgr-cluster-show"/>,
-      <xref linkend="repmgrd-pausing"/>,
-      <xref linkend="repmgr-daemon-start"/>,
-      <xref linkend="repmgr-daemon-stop"/>
-    </para>
-  </refsect1>
-</refentry>

doc/repmgr-service-unpause.xml

@@ -1,121 +0,0 @@
-<refentry id="repmgr-service-unpause">
-  <indexterm>
-    <primary>repmgr service unpause</primary>
-  </indexterm>
-
-  <indexterm>
-    <primary>repmgrd</primary>
-    <secondary>unpausing</secondary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr service unpause</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr service unpause</refname>
-    <refpurpose>Instruct all &repmgrd; instances in the replication cluster to resume failover operations</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      This command can be run on any active node in the replication cluster to instruct all
-      running &repmgrd; instances to &quot;unpause&quot;
-      (following a previous execution of <xref linkend="repmgr-service-pause"/>)
-      and resume normal failover/monitoring operation.
-    </para>
-
-    <note>
-      <para>
-        It's important to wait a few seconds after restarting PostgreSQL on any node before running
-        <command>repmgr service pause</command>, as the &repmgrd; instance
-        on the restarted node will take a second or two before it has updated its status.
-      </para>
-    </note>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Prerequisites</title>
-    <para>
-      PostgreSQL must be accessible on all nodes (using the <varname>conninfo</varname> string shown by
-      <link linkend="repmgr-cluster-show"><command>repmgr cluster show</command></link>)
-      from the node where <command>repmgr service pause</command> is executed.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Execution</title>
-    <para>
-     <command>repmgr service unpause</command> can be executed on any active node in the
-      replication cluster. A valid <filename>repmgr.conf</filename> file is required.
-      It will have no effect on nodes which are not already paused.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Example</title>
-    <para>
-    <programlisting>
-$ repmgr -f /etc/repmgr.conf service unpause
-NOTICE: node 1 (node1) unpaused
-NOTICE: node 2 (node2) unpaused
-NOTICE: node 3 (node3) unpaused</programlisting>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Options</title>
-    <variablelist>
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check if nodes are reachable but don't unpause &repmgrd;.
-          </para>
-        </listitem>
-      </varlistentry>
-    </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr service unpause</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            &repmgrd; could be unpaused on all nodes.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_REPMGRD_PAUSE (26)</option></term>
-        <listitem>
-          <para>
-           &repmgrd; could not be unpaused on one or mode nodes.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-      <xref linkend="repmgr-service-pause"/>,
-      <xref linkend="repmgr-service-status"/>,
-      <xref linkend="repmgrd-pausing"/>,
-      <xref linkend="repmgr-daemon-start"/>,
-      <xref linkend="repmgr-daemon-stop"/>
-    </para>
-  </refsect1>
-</refentry>
-

doc/repmgr-standby-clone.xml

@@ -1,487 +0,0 @@
-<refentry id="repmgr-standby-clone">
-  <indexterm>
-    <primary>repmgr standby clone</primary>
-    <seealso>cloning</seealso>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr standby clone</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr standby clone</refname>
-    <refpurpose>clone a PostgreSQL standby node from another PostgreSQL node</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      <command>repmgr standby clone</command> clones a PostgreSQL node from another
-      PostgreSQL node, typically the primary, but optionally from any other node in
-      the cluster or from Barman. It creates the replication configuration required
-      to attach the cloned node to the primary node (or another standby, if cascading replication
-      is in use).
-    </para>
-    <note>
-      <simpara>
-        <command>repmgr standby clone</command> does not start the standby, and after cloning
-        a standby, the command <command>repmgr standby register</command> must be executed to
-        notify &repmgr; of its existence.
-      </simpara>
-    </note>
-
-  </refsect1>
-
-
-  <refsect1 id="repmgr-standby-clone-config-file-copying" xreflabel="Copying configuration files">
-   <title>Handling configuration files</title>
-
-   <para>
-    Note that by default, all configuration files in the source node's data
-    directory will be copied to the cloned node.  Typically these will be
-    <filename>postgresql.conf</filename>, <filename>postgresql.auto.conf</filename>,
-    <filename>pg_hba.conf</filename> and <filename>pg_ident.conf</filename>.
-    These may require modification before the standby is started.
-   </para>
-   <para>
-    In some cases (e.g. on Debian or Ubuntu Linux installations), PostgreSQL's
-    configuration files are located outside of the data directory and will
-    not be copied by default. &repmgr; can copy these files, either to the same
-    location on the standby server (provided appropriate directory and file permissions
-    are available), or into the standby's data directory. This requires passwordless
-    SSH access to the primary server. Add the option <option>--copy-external-config-files</option>
-    to the <command>repmgr standby clone</command> command; by default files will be copied to
-    the same path as on the upstream server. Note that the user executing <command>repmgr</command>
-    must have write access to those directories.
-   </para>
-   <para>
-    To have the configuration files placed in the standby's data directory, specify
-    <literal>--copy-external-config-files=pgdata</literal>, but note that
-    any include directives in the copied files may need to be updated.
-   </para>
-
-   <note>
-	 <para>
-	   When executing <command>repmgr standby clone</command> with the
-	   <option>--copy-external-config-files</option> aand <option>--dry-run</option>
-	   options, &repmgr; will check the SSH connection to the source node, but
-	   will not verify whether the files can actually be copied.
-	 </para>
-	 <para>
-	   During the actual clone operation, a check will be made before the database itself
-	   is cloned to determine whether the files can actually be copied; if any problems are
-	   encountered, the clone operation will be aborted, enabling the user to fix
-	   any issues before retrying the clone operation.
-	 </para>
-   </note>
-
-   <tip>
-    <simpara>
-     For reliable configuration file management we recommend using a
-     configuration management tool such as Ansible, Chef, Puppet or Salt.
-    </simpara>
-   </tip>
-
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-clone-recovery-conf">
-    <title>Customising replication configuration</title>
-    <indexterm>
-     <primary>recovery.conf</primary>
-     <secondary>customising with &quot;repmgr standby clone&quot;</secondary>
-    </indexterm>
-
-	<indexterm>
-     <primary>replication configuration</primary>
-     <secondary>customising with &quot;repmgr standby clone&quot;</secondary>
-    </indexterm>
-
-
-   <para>
-     By default, &repmgr; will create a minimal replication configuration
-     containing following parameters:
-   </para>
-
-   <itemizedlist spacing="compact" mark="bullet">
-
-     <listitem>
-       <simpara><varname>primary_conninfo</varname></simpara>
-     </listitem>
-
-     <listitem>
-       <simpara><varname>primary_slot_name</varname> (if replication slots in use)</simpara>
-     </listitem>
-
-   </itemizedlist>
-
-   <para>
-     For PostgreSQL 11 and earlier, these parameters will also be set:
-   </para>
-
-   <itemizedlist spacing="compact" mark="bullet">
-     <listitem>
-       <simpara><varname>standby_mode</varname> (always <literal>'on'</literal>)</simpara>
-     </listitem>
-
-     <listitem>
-       <simpara><varname>recovery_target_timeline</varname> (always <literal>'latest'</literal>)</simpara>
-     </listitem>
-   </itemizedlist>
-
-
-   <para>
-     The following additional parameters can be specified in <filename>repmgr.conf</filename>
-     for inclusion in the replication configuration:
-   </para>
-
-   <itemizedlist spacing="compact" mark="bullet">
-
-     <listitem>
-       <simpara><varname>restore_command</varname></simpara>
-     </listitem>
-
-     <listitem>
-       <simpara><varname>archive_cleanup_command</varname></simpara>
-     </listitem>
-
-     <listitem>
-       <simpara><varname>recovery_min_apply_delay</varname></simpara>
-     </listitem>
-
-   </itemizedlist>
-
-   <note>
-     <para>
-       We recommend using <ulink url="https://www.pgbarman.org/">Barman</ulink> to manage
-       WAL file archiving. For more details on combining &repmgr; and <application>Barman</application>,
-       in particular using <varname>restore_command</varname> to configure Barman as a backup source of
-       WAL files, see <xref linkend="cloning-from-barman"/>.
-     </para>
-   </note>
-
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-clone-wal-management">
-   <title>Managing WAL during the cloning process</title>
-   <para>
-    When initially cloning a standby, you will need to ensure
-    that all required WAL files remain available while the cloning is taking
-    place. To ensure this happens when using the default <command>pg_basebackup</command> method,
-    &repmgr; will set <command>pg_basebackup</command>'s <literal>--wal-method</literal>
-    parameter to <literal>stream</literal>,
-    which will ensure all WAL files generated during the cloning process are
-    streamed in parallel with the main backup. Note that this requires two
-    replication connections to be available (&repmgr; will verify sufficient
-    connections are available before attempting to clone, and this can be checked
-    before performing the clone using the <literal>--dry-run</literal> option).
-   </para>
-   <para>
-    To override this behaviour, in <filename>repmgr.conf</filename> set
-    <command>pg_basebackup</command>'s <literal>--wal-method</literal>
-    parameter to <literal>fetch</literal>:
-    <programlisting>
-      pg_basebackup_options='--wal-method=fetch'</programlisting>
-
-    and ensure that <literal>wal_keep_segments</literal> (PostgreSQL 13 and later:
-    <literal>wal_keep_size</literal>) is set to an appropriately high value. Note
-    however that this is not a particularly reliable way of ensuring sufficient
-    WAL is retained and is not recommended.
-    See the <ulink url="https://www.postgresql.org/docs/current/app-pgbasebackup.html">
-    pg_basebackup</ulink> documentation for details.
-   </para>
-
-   <note>
-    <simpara>
-      If using PostgreSQL 9.6 or earlier, replace <literal>--wal-method</literal>
-      with <literal>--xlog-method</literal>.
-    </simpara>
-   </note>
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-clone-wal-directory">
-
-   <title>Placing WAL files into a different directory</title>
-
-   <para>
-     To ensure that WAL files are placed in a directory outside of the main data
-     directory (e.g. to keep them on a separate disk for performance reasons),
-     specify the location with  <option>--waldir</option>
-     (PostgreSQL 9.6 and earlier: <option>--xlogdir</option>) in
-     the <filename>repmgr.conf</filename> parameter <option>pg_basebackup_options</option>,
-     e.g.:
-     <programlisting>
-pg_basebackup_options='--waldir=/path/to/wal-directory'</programlisting>
-     This setting will also be honored by &repmgr; when cloning from Barman
-     (&repmgr; 5.2 and later).
-   </para>
-
-  </refsect1>
-
-<!-- don't rename this id as it may be used in external links -->
-  <refsect1 id="repmgr-standby-create-recovery-conf">
-
-   <title>Using a standby cloned by another method</title>
-
-   <indexterm>
-     <primary>replication configuration</primary>
-     <secondary>generating for a standby cloned by another method</secondary>
-   </indexterm>
-
-   <indexterm>
-     <primary>recovery.conf</primary>
-     <secondary>generating for a standby cloned by another method</secondary>
-   </indexterm>
-
-   <para>
-     &repmgr; supports standbys cloned by another method (e.g. using <application>barman</application>'s
-     <command><ulink url="https://docs.pgbarman.org/#recover">barman recover</ulink></command> command).
-   </para>
-   <para>
-     To integrate the standby as a &repmgr; node, once the standby has been cloned,
-     ensure the <filename>repmgr.conf</filename>
-     file is created for the node, and that it has been registered using
-     <command><link linkend="repmgr-standby-register">repmgr standby register</link></command>.
-   </para>
-   <tip>
-     <para>
-       To register a standby which is not running, execute
-       <link linkend="repmgr-standby-register">repmgr standby register --force</link>
-       and provide the connection details for the primary.
-     </para>
-     <para>
-       See <xref linkend="repmgr-standby-register-inactive-node"/> for more details.
-     </para>
-   </tip>
-   <para>
-     Then execute the command <command>repmgr standby clone --replication-conf-only</command>.
-     This will create the <filename>recovery.conf</filename> file needed to attach
-     the node to its upstream (in PostgreSQL 12 and later: append replication configuration
-     to <filename>postgresql.auto.conf</filename>), and will also create a replication slot on the
-     upstream node if required.
-   </para>
-   <para>
-     The upstream node must be running so the correct replication configuration can be obtained.
-   </para>
-   <para>
-     If the standby is running, the replication configuration will not be written unless the
-     <option>-F/--force</option> option is provided.
-   </para>
-   <tip>
-     <para>
-       Execute <command>repmgr standby clone --replication-conf-only --dry-run</command>
-       to check the prerequisites for creating the recovery configuration,
-       and display the configuration changes which would be made without actually
-	   making any changes.
-     </para>
-   </tip>
-   <para>
-     In PostgreSQL 13 and later, the PostgreSQL configuration must be reloaded for replication
-     configuration changes to take effect.
-   </para>
-   <para>
-     In PostgreSQL 12 and earlier, the PostgreSQL instance must be restarted for replication
-     configuration changes to take effect.
-   </para>
-
-
-  </refsect1>
-
-  <refsect1>
-
-    <title>Options</title>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>-d, --dbname=CONNINFO</option></term>
-        <listitem>
-          <para>
-            Connection string of the upstream node to use for cloning.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually clone the standby.
-          </para>
-          <para>
-            If <option>--replication-conf-only</option> specified, the contents of
-            the generated recovery configuration will be displayed
-            but not written.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>-c, --fast-checkpoint</option></term>
-        <listitem>
-          <para>
-            Force fast checkpoint (not effective when cloning from Barman).
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--copy-external-config-files[={samepath|pgdata}]</option></term>
-        <listitem>
-          <para>
-            Copy configuration files located outside the data directory on the source
-            node to the same path on the standby (default) or to the
-            PostgreSQL data directory.
-          </para>
-          <para>
-            Note that to be able to use this option, the &repmgr; user must be a superuser or
-            member of the <literal>pg_read_all_settings</literal> predefined role.
-            If this is not the case, provide a valid superuser with the
-            <option>-S</option>/<option>--superuser</option> option.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--no-upstream-connection</option></term>
-        <listitem>
-          <para>
-            When using Barman, do not connect to upstream node.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><option>--recovery-min-apply-delay</option></term>
-        <listitem>
-          <para>
-            Set PostgreSQL configuration <option>recovery_min_apply_delay</option> parameter
-            to the provided value.
-          </para>
-          <para>
-            This overrides any <option>recovery_min_apply_delay</option> provided via
-            <filename>repmgr.conf</filename>.
-          </para>
-          <para>
-            For more details on this parameter, see:
-            <ulink url="https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-RECOVERY-MIN-APPLY-DELAY">recovery_min_apply_delay</ulink>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>-R, --remote-user=USERNAME</option></term>
-        <listitem>
-          <para>
-            Remote system username for SSH operations (default: current local system username).
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--replication-conf-only</option></term>
-        <listitem>
-          <para>
-            Create recovery configuration for a previously cloned instance.
-          </para>
-		  <para>
-			In PostgreSQL 12 and later, the replication configuration will be
-			written to <filename>postgresql.auto.conf</filename>.
-		  </para>
-		  <para>
-			In PostgreSQL 11 and earlier, the replication configuration will be
-			written to <filename>recovery.conf</filename>.
-		  </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--replication-user</option></term>
-        <listitem>
-          <para>
-            User to make replication connections with (optional, not usually required).
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>-S</option>/<option>--superuser</option></term>
-        <listitem>
-          <para>
-            The name of a valid PostgreSQL superuser can  be provided with this option.
-          </para>
-          <para>
-            This is only required if the <option>--copy-external-config-files</option> was provided
-            and the &repmgr; user is not a superuser or member of the <literal>pg_read_all_settings</literal>
-            predefined role.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><option>--upstream-conninfo</option></term>
-        <listitem>
-          <para>
-            <literal>primary_conninfo</literal> value to include in the recovery configuration
-            when the intended upstream server does not yet exist.
-          </para>
-          <para>
-            Note that &repmgr; may modify the provided value, in particular to set the
-            correct <literal>application_name</literal>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--upstream-node-id</option></term>
-        <listitem>
-          <para>
-            ID of the upstream node to replicate from (optional, defaults to primary node)
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--verify-backup</option></term>
-        <listitem>
-          <para>
-            <!-- update link after Pg13 release -->
-            Verify a cloned node using the
-            <ulink url="https://www.postgresql.org/docs/13/app-pgverifybackup.html">pg_verifybackup</ulink>
-            utility (PostgreSQL 13 and later).
-          </para>
-          <para>
-            This option can currently only be used when cloning directly from an upstream
-            node.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--without-barman </option></term>
-        <listitem>
-          <para>
-            Do not use Barman even if configured.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-clone-events">
-    <title>Event notifications</title>
-    <para>
-      A <literal>standby_clone</literal> <link linkend="event-notifications">event notification</link> will be generated.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-      See <xref linkend="cloning-standbys"/> for details about various aspects of cloning.
-    </para>
-  </refsect1>
-</refentry>
-

doc/repmgr-standby-follow.xml

@@ -1,271 +0,0 @@
-<refentry id="repmgr-standby-follow">
-  <indexterm>
-    <primary>repmgr standby follow</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr standby follow</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr standby follow</refname>
-    <refpurpose>attach a running standby to a new upstream node</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-
-    <para>
-      Attaches the standby (&quot;follow candidate&quot;) to a new upstream node
-      (&quot;follow target&quot;). Typically this will be the primary, but this
-      command can also be used to attach the standby to another standby.
-    </para>
-
-    <para>
-      This command requires a valid <filename>repmgr.conf</filename> file for the standby,
-      either specified explicitly with <literal>-f/--config-file</literal> or located in a
-      default location; no additional arguments are required.
-    </para>
-
-    <para>The standby node (&quot;follow candidate&quot;) <emphasis>must</emphasis>
-      be running. If the new upstream (&quot;follow target&quot;) is not the primary,
-      the cluster primary <emphasis>must</emphasis> be running and accessible from the
-      standby node.
-    </para>
-
-    <tip>
-      <para>
-        To re-add an inactive node to the replication cluster, use
-        <xref linkend="repmgr-node-rejoin"/>.
-      </para>
-    </tip>
-
-    <para>
-      By default &repmgr; will attempt to attach the standby to the current primary.
-      If <option>--upstream-node-id</option> is provided, &repmgr; will attempt
-      to attach the standby to the specified node, which can be another standby.
-    </para>
-
-    <para>
-      In PostgreSQL 12 and earlier, this command will force a restart of PostgreSQL on the standby node.
-    </para>
-
-    <para>
-      In PostgreSQL 13 and later, by default this command will signal PostgreSQL to reload its
-      configuration, which will cause PostgreSQL to follow the new upstream without
-      a restart. If this behaviour is not desired for whatever reason, the configuration
-      file parameter <varname>standby_follow_restart</varname> can be set <literal>true</literal>
-      to always force a restart.
-    </para>
-
-    <para>
-      <command>repmgr standby follow</command> will wait up to
-      <varname>standby_follow_timeout</varname> seconds (default: <literal>30</literal>)
-      to verify the standby has actually connected to the new upstream node.
-    </para>
-
-    <note>
-      <para>
-        If <option>recovery_min_apply_delay</option> is set for the standby, it
-        will not attach to the new upstream node until it has replayed available
-        WAL.
-      </para>
-      <para>
-        Conversely, if the standby is attached to an upstream standby
-        which has <option>recovery_min_apply_delay</option> set, the upstream
-        standby's replay state may actually be behind that of its new downstream node.
-      </para>
-    </note>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Example</title>
-    <para>
-      <programlisting>
-      $ repmgr -f /etc/repmgr.conf standby follow
-      INFO: setting node 3's primary to node 2
-      NOTICE: restarting server using "pg_ctl -l /var/log/postgres/startup.log -w -D '/var/lib/postgres/data' restart"
-      waiting for server to shut down........ done
-      server stopped
-      waiting for server to start.... done
-      server started
-      NOTICE: STANDBY FOLLOW successful
-      DETAIL: node 3 is now attached to node 2</programlisting>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Options</title>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually follow a new upstream node.
-          </para>
-          <para>
-            This will also verify whether the standby is capable of following the new upstream node.
-          </para>
-          <important>
-            <para>
-              If a standby was turned into a primary by removing <filename>recovery.conf</filename>
-              (<application>PostgreSQL 12</application> and later: <filename>standby.signal</filename>),
-              &repmgr; will <emphasis>not</emphasis> be able to determine whether that primary's timeline
-              has diverged from the timeline of the standby (&quot;follow candidate&quot;).
-            </para>
-            <para>
-              We recommend always to use <link linkend="repmgr-standby-promote"><command>repmgr standby promote</command></link>
-              to promote a standby to primary, as this will ensure that the new primary
-              will perform a timeline switch (making it practical to check for timeline divergence)
-              and also that &repmgr; metadata is updated correctly.
-            </para>
-          </important>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--upstream-node-id</option></term>
-        <listitem>
-          <para>
-            Node ID of the new upstream node (&quot;follow target&quot;).
-          </para>
-          <para>
-            If not provided, &repmgr; will attempt to follow the current primary node.
-          </para>
-          <para>
-            Note that when using &repmgrd;, <option>--upstream-node-id</option>
-            should always be configured;
-            see <link linkend="repmgrd-automatic-failover-configuration">Automatic failover configuration</link>
-            for details.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>-w</option></term>
-        <term><option>--wait</option></term>
-        <listitem>
-          <para>
-            Wait for a primary to appear. &repmgr; will wait for up to
-            <varname>primary_follow_timeout</varname> seconds
-            (default: 60 seconds) to verify that the standby is following the new primary.
-            This value can be defined in <filename>repmgr.conf</filename>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>Execution</title>
-
-    <para>
-      Execute with the <literal>--dry-run</literal> option to test the follow operation as
-      far as possible, without actually changing the status of the node.
-    </para>
-
-    <para>
-      Note that &repmgr; will first attempt to determine whether the standby
-      (&quot;follow candidate&quot;) is capable of following the
-      new upstream node (&quot;follow target&quot;).
-    </para>
-    <para>
-      If, for example, the new upstream node has diverged from this node's timeline,
-      for example if the new upstream node was promoted to primary while this node
-      was still attached to the original primary, it will <emphasis>not</emphasis>
-      be possible to follow the new upstream node, and &repmgr; will emit an error
-      message like this:
-      <programlisting>
-ERROR: this node cannot attach to follow target node &quot;node3&quot; (ID 3)
-DETAIL: follow target server's timeline 2 forked off current database system timeline 1 before current recovery point 0/6108880</programlisting>
-    </para>
-    <para>
-      In this case, it may be possible to have this node follow the new upstream
-      using <command><link linkend="repmgr-node-rejoin">repmgr node rejoin</link></command>
-      with the <option>--force-rewind</option> to execute <command>pg_rewind</command>.
-      This does mean that transactions which exist on this node, but not the new upstream,
-      will be lost.
-    </para>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr standby follow</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            The follow operation succeeded; or if <option>--dry-run</option> was provided,
-            no issues were detected which would prevent the follow operation.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_BAD_CONFIG (1)</option></term>
-        <listitem>
-          <para>
-            A configuration issue was detected which prevented &repmgr; from
-            continuing with the follow operation.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_NO_RESTART (4)</option></term>
-        <listitem>
-          <para>
-            The node could not be restarted.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_DB_CONN (6)</option></term>
-        <listitem>
-          <para>
-            &repmgr; was unable to establish a database connection to one of the nodes.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_FOLLOW_FAIL (23)</option></term>
-        <listitem>
-          <para>
-            &repmgr; was unable to complete the follow command.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-follow-events">
-    <title>Event notifications</title>
-    <para>
-      A <literal>standby_follow</literal> <link linkend="event-notifications">event notification</link> will be generated.
-    </para>
-    <para>
-      If provided, &repmgr; will substitute the placeholders <literal>%p</literal> with the node ID of the node
-      being followed, <literal>%c</literal> with its <literal>conninfo</literal> string, and
-      <literal>%a</literal> with its node name.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-     <xref linkend="repmgr-node-rejoin"/>
-    </para>
-  </refsect1>
-</refentry>

doc/repmgr-standby-promote.xml

@@ -1,345 +0,0 @@
-<refentry id="repmgr-standby-promote">
-  <indexterm>
-    <primary>repmgr standby promote</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr standby promote</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr standby promote</refname>
-    <refpurpose>promote a standby to a primary</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      Promotes a standby to a primary if the current primary has failed. This
-      command requires a valid <filename>repmgr.conf</filename> file for the standby, either
-      specified explicitly with <literal>-f/--config-file</literal> or located in a
-      default location; no additional arguments are required.
-    </para>
-    <important>
-      <para>
-        If &repmgrd; is active, you must execute
-        <command><link linkend="repmgr-service-pause">repmgr service pause</link></command>
-        (&repmgr; 4.2 - 4.4: <command><link linkend="repmgr-service-pause">repmgr service pause</link></command>)
-        to temporarily disable &repmgrd; while making any changes
-        to the replication cluster.
-      </para>
-    </important>
-
-    <para>
-      If the standby promotion succeeds, the server will not need to be
-      restarted. However any other standbys will need to follow the new primary,
-      and will need to be restarted to do this.
-    </para>
-    <para>
-      Beginning with <link linkend="release-4.4">repmgr 4.4</link>,
-      the option <option>--siblings-follow</option> can be used to have
-      all other standbys (and a witness server, if in use)
-	  follow the new primary.
-    </para>
-
-    <note>
-      <para>
-        If using &repmgrd;, when invoking
-        <command>repmgr standby promote</command> (either directly via
-        the <option>promote_command</option>, or in a script called
-        via <option>promote_command</option>), <option>--siblings-follow</option>
-        <emphasis>must not</emphasis> be included as a
-        command line option for <command>repmgr standby promote</command>.
-      </para>
-    </note>
-
-    <para>
-      In <link linkend="release-4.3">repmgr 4.3</link> and earlier,
-      <command><link linkend="repmgr-standby-follow">repmgr standby follow</link></command>
-      must be executed on each standby individually.
-    </para>
-
-    <para>
-      &repmgr; will wait for up to <varname>promote_check_timeout</varname> seconds
-      (default: <literal>60</literal>) to verify that the standby has been promoted, and will
-      check the promotion every <varname>promote_check_interval</varname> seconds (default: 1 second).
-      Both values can be defined in <filename>repmgr.conf</filename>.
-    </para>
-
-    <warning>
-      <para>
-        In PostgreSQL 12 and earlier, if WAL replay is paused on the standby, and not all
-        WAL files on the standby have been replayed, &repmgr; will not attempt to promote it.
-      </para>
-      <para>
-        This is because if WAL replay is paused, PostgreSQL itself will not react to a promote command
-        until WAL replay is resumed and all pending WAL has been replayed. This means
-        attempting to promote PostgreSQL in this state will leave PostgreSQL in a condition where the
-        promotion may occur at a unpredictable point in the future.
-      </para>
-      <para>
-        Note that if the standby is in archive recovery, &repmgr; will not be able to determine
-        if more WAL is pending replay, and will abort the promotion attempt if WAL replay is paused.
-      </para>
-      <para>
-        This restriction does <emphasis>not</emphasis> apply to PostgreSQL 13 and later.
-      </para>
-    </warning>
-
-  </refsect1>
-
-
-
-  <refsect1>
-    <title>Example</title>
-    <para>
-      <programlisting>
-      $ repmgr -f /etc/repmgr.conf standby promote
-      NOTICE: promoting standby to primary
-      DETAIL: promoting server "node2" (ID: 2) using "pg_ctl -l /var/log/postgres/startup.log -w -D '/var/lib/postgres/data' promote"
-      server promoting
-      NOTICE: STANDBY PROMOTE successful
-      DETAIL: server "node2" (ID: 2) was successfully promoted to primary</programlisting>
-    </para>
-  </refsect1>
-
-
-  <refsect1>
-    <title>User permission requirements</title>
-    <para><emphasis>pg_promote() (PostgreSQL 12 and later)</emphasis></para>
-    <para>
-      From PostgreSQL 12, &repmgr; will attempt to use the built-in <function>pg_promote()</function>
-      function to promote a standby to primary.
-    </para>
-    <para>
-      By default, execution of <function>pg_promote()</function> is restricted to superusers.
-      If the <literal>repmgr</literal> user does not have permission to execute
-      <function>pg_promote()</function>, &repmgr; will fall back to using &quot;<command>pg_ctl promote</command>&quot;.
-    </para>
-    <tip>
-      <para>
-        Execute <command>repmgr standby promote</command> with the <option>--dry-run</option>
-        to check whether the &repmgr; user has permission to execute <function>pg_promote()</function>.
-      </para>
-      <para>
-        If the <literal>repmgr</literal> user is not a superuser, execution permission for this
-        function can be granted with e.g.:
-        <programlisting>
-    GRANT EXECUTE ON FUNCTION pg_catalog.pg_promote TO repmgr</programlisting>
-      </para>
-      <para>
-        Note that permissions are only effective for the database they are granted in, so
-        this <emphasis>must</emphasis> be executed in the &repmgr; database to be effective.
-      </para>
-    </tip>
-    <para>
-      For more details on <function>pg_promote()</function>, see the
-      <ulink url="https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-RECOVERY-CONTROL-TABLE">PostgreSQL documentation</ulink>.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Options</title>
-    <variablelist>
-      <varlistentry>
-
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check if this node can be promoted, but don't carry out the promotion.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--siblings-follow</option></term>
-        <listitem>
-          <para>
-            Have all sibling nodes (nodes formerly attached to the same upstream
-            node as the promotion candidate) follow this node after it has been promoted.
-          </para>
-		  <para>
-			Note that a witness server, if in use, is also
-			counted as a &quot;sibling node&quot; as it needs to be instructed to
-			synchronise its metadata with the new primary.
-		  </para>
-          <important>
-            <para>
-              Do <emphasis>not</emphasis> provide this option when configuring
-              &repmgrd;'s <option>promote_command</option>.
-            </para>
-          </important>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>-F</option></term>
-        <term><option>--force</option></term>
-        <listitem>
-          <para>
-            Ignore warnings and continue anyway.
-          </para>
-          <para>
-            This option is relevant in the following situations if <option>--siblings-follow</option> was specified:
-            <itemizedlist spacing="compact" mark="bullet">
-              <listitem>
-                <simpara>
-                  If one or more sibling nodes was not reachable via SSH, the standby will be promoted anyway.
-                </simpara>
-              </listitem>
-              <listitem>
-                <simpara>
-                  If the promotion candidate has insufficient free walsenders to accommodate the standbys which will
-                  be attached to it, the standby will be promoted anyway.
-                </simpara>
-              </listitem>
-              <listitem>
-                <simpara>
-                  If replication slots are in use but the promotion candidate has insufficient free replication slots
-                  to accommodate the standbys which will be attached to it, the standby will be promoted anyway.
-                </simpara>
-              </listitem>
-            </itemizedlist>
-          </para>
-          <para>
-            Note that if the <option>-F</option>/<option>--force</option> option is used when any of the above
-            situations is encountered, the onus is on the user to manually resolve any resulting issues.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>Configuration file settings</title>
-   <para>
-     The following parameters in <filename>repmgr.conf</filename> are relevant to the
-     promote operation:
-    </para>
-
-    <para>
-      <itemizedlist spacing="compact" mark="bullet">
-
-       <listitem>
-        <indexterm>
-          <primary>promote_check_interval</primary>
-          <secondary>with &quot;repmgr standby promote &quot;</secondary>
-        </indexterm>
-         <simpara>
-           <literal>promote_check_interval</literal>:
-           interval (in seconds, default: 1 second) to wait between each check
-           to determine whether the standby has been promoted.
-		 </simpara>
-	   </listitem>
-
-       <listitem>
-        <indexterm>
-          <primary>promote_check_timeout</primary>
-          <secondary>with &quot;repmgr standby promote &quot;</secondary>
-        </indexterm>
-         <simpara>
-           <literal>promote_check_timeout</literal>:
-           time (in seconds, default: 60 seconds) to wait to verify that the standby has been promoted
-           before exiting with <literal>ERR_PROMOTION_FAIL</literal>.
-		 </simpara>
-	   </listitem>
-
-       <listitem>
-        <indexterm>
-          <primary>service_promote_command</primary>
-          <secondary>with &quot;repmgr standby promote &quot;</secondary>
-        </indexterm>
-         <simpara>
-           <literal>service_promote_command</literal>:
-           a command which will be executed instead of <command>pg_ctl promote</command>
-           or (in PostgreSQL 12 and later) <function>pg_promote()</function>.
-         </simpara>
-         <simpara>
-           This is intended for systems which provide a package-level promote command,
-           such as Debian's <application>pg_ctlcluster</application>, to promote the
-           PostgreSQL from standby to primary.
-         </simpara>
-       </listitem>
-
-	  </itemizedlist>
-	</para>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      Following exit codes can be emitted by <command>repmgr standby promote</command>:
-    </para>
-    <variablelist>
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            The standby was successfully promoted to primary.
-          </para>
-        </listitem>
-      </varlistentry>
-
-     <varlistentry>
-        <term><option>ERR_DB_CONN (6)</option></term>
-        <listitem>
-          <para>
-            &repmgr; was unable to connect to the local PostgreSQL node.
-          </para>
-          <para>
-            PostgreSQL must be running before the node can be promoted.
-          </para>
-        </listitem>
-      </varlistentry>
-
-     <varlistentry>
-       <term><option>ERR_PROMOTION_FAIL (8)</option></term>
-        <listitem>
-          <para>
-            The node could not be promoted to primary for one of the following
-            reasons:
-            <itemizedlist spacing="compact" mark="bullet">
-
-              <listitem>
-                <simpara>
-                  there is an existing primary node in the replication cluster
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  the node is not a standby
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  WAL replay is paused on the node
-                </simpara>
-              </listitem>
-
-              <listitem>
-                <simpara>
-                  execution of the PostgreSQL promote command failed
-                </simpara>
-              </listitem>
-
-            </itemizedlist>
-          </para>
-        </listitem>
-     </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-
-  <refsect1 id="repmgr-standby-promote-events">
-    <title>Event notifications</title>
-    <para>
-      A <literal>standby_promote</literal> <link linkend="event-notifications">event notification</link> will be generated.
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr-standby-register.xml

@@ -1,197 +0,0 @@
-<refentry id="repmgr-standby-register" xreflabel="repmgr standby register">
-  <indexterm>
-    <primary>repmgr standby register</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr standby register</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr standby register</refname>
-    <refpurpose>add a standby's information to the &repmgr; metadata</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      <command>repmgr standby register</command> adds a standby's information to
-      the &repmgr; metadata. This command needs to be executed to enable
-      promote/follow operations and to allow &repmgrd; to work with the node.
-      An existing standby can be registered using this command. Execute with the
-      <literal>--dry-run</literal> option to check what would happen without actually registering the
-      standby.
-    </para>
-
-    <note>
-      <para>
-        If providing the configuration file location with <literal>-f/--config-file</literal>,
-        avoid using a relative path, as &repmgr; stores the configuration file location
-        in the repmgr metadata for use when &repmgr; is executed remotely (e.g. during
-        <xref linkend="repmgr-standby-switchover"/>). &repmgr; will attempt to convert the
-          a relative path into an absolute one, but this may not be the same as the path you
-          would explicitly provide (e.g. <filename>./repmgr.conf</filename> might be converted
-          to <filename>/path/to/./repmgr.conf</filename>, whereas you'd normally write
-          <filename>/path/to/repmgr.conf</filename>).
-      </para>
-    </note>
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-register-wait-start" xreflabel="repmgr standby register --wait-start">
-   <title>Waiting for the the standby to start</title>
-   <para>
-     By default, &repmgr; will wait 30 seconds for the standby to become available before
-     aborting with a connection error. This is useful when setting up a standby from a script,
-     as the standby may not have fully started up by the time <command>repmgr standby register</command>
-     is executed.
-   </para>
-   <para>
-     To change the timeout, pass the desired value with the <literal>--wait-start</literal> option.
-     A value of <literal>0</literal> will disable the timeout.
-   </para>
-   <para>
-     The timeout will be ignored if <literal>-F/--force</literal> was provided.
-   </para>
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-register-wait-sync" xreflabel="repmgr standby register --wait-sync">
-   <title>Waiting for the registration to propagate to the standby</title>
-   <para>
-     Depending on your environment and workload, it may take some time for the standby's node record
-     to propagate from the primary to the standby. Some actions (such as starting
-     &repmgrd;) require that the standby's node record
-     is present and up-to-date to function correctly.
-   </para>
-   <para>
-    By providing the option <option>--wait-sync</option> to the
-    <command>repmgr standby register</command> command, &repmgr; will wait
-    until the record is synchronised before exiting. An optional timeout (in
-    seconds) can be added to this option (e.g. <option>--wait-sync=60</option>).
-   </para>
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-register-inactive-node" xreflabel="Registering an inactive node">
-   <title>Registering an inactive node</title>
-   <para>
-    Under some circumstances you may wish to register a standby which is not
-    yet running; this can be the case when using provisioning tools to create
-    a complex replication cluster, or if the node was not cloned by &repmgr;.
-   </para>
-   <para>
-    In this case, by using the <option>-F/--force</option>
-    option and providing the connection parameters to the primary server,
-    the standby can be registered even if it has not yet been started.
-   </para>
-   <tip>
-     <para>
-       Connection parameters can either be provided either as a <literal>conninfo</literal> string
-       (e.g. <option>-d 'host=node1 user=repmgr'</option> or as individual connection parameters
-        (<option>-h/--host</option>, <option>-d/--dbname</option>,
-       <option>-U/--user</option>, <option>-p/--port</option> etc.).
-     </para>
-   </tip>
-
-   <para>
-    Similarly, with cascading replication it may be necessary to register
-    a standby whose upstream node has not yet been registered - in this case,
-    using <option>-F/--force</option> will result in the creation of an inactive placeholder
-    record for the upstream node, which will however later need to be registered
-    with the <option>-F/--force</option> option too.
-   </para>
-   <para>
-    When used with <command>repmgr standby register</command>, care should be taken that use of the
-    <option>-F/--force</option> option does not result in an incorrectly configured cluster.
-   </para>
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-register-node-cloned-other-source">
-    <title>Registering a node not cloned by repmgr</title>
-    <para>
-      If you've cloned a standby using another method (e.g. <application>barman</application>'s
-     <command><ulink url="https://docs.pgbarman.org/#recover">barman recover</ulink></command>
-     command), register the node as detailed in section
-     <xref linkend="repmgr-standby-register-inactive-node"/> then execute
-     <link linkend="repmgr-standby-create-recovery-conf">repmgr standby clone --replication-conf-only</link>
-     to generate the appropriate replication configuration.
-    </para>
-  </refsect1>
-
-  <refsect1>
-
-    <title>Options</title>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually register the standby.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-       <term><option>-F</option>/<option>--force</option></term>
-        <listitem>
-          <para>
-            Overwrite an existing node record
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><option>--upstream-node-id</option></term>
-        <listitem>
-          <para>
-            ID of the upstream node to replicate from (optional)
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--wait-start</option></term>
-        <listitem>
-          <para>
-            wait for the standby to start (timeout in seconds, default 30 seconds)
-          </para>
-        </listitem>
-      </varlistentry>
-
-     <varlistentry>
-        <term><option>--wait-sync</option></term>
-        <listitem>
-          <para>
-            wait for the node record to synchronise to the standby (optional timeout in seconds)
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-register-events">
-    <title>Event notifications</title>
-    <para>
-      A <literal>standby_register</literal> <link linkend="event-notifications">event notification</link>
-      will be generated immediately after the node record is updated on the primary.
-    </para>
-
-    <para>
-      If the <option>--wait-sync</option> option is provided, a <literal>standby_register_sync</literal>
-      event notification  will be generated immediately after the node record has synchronised to the
-      standby.
-    </para>
-
-    <para>
-      If provided, &repmgr; will substitute the placeholders <literal>%p</literal> with the node ID of the
-      primary node, <literal>%c</literal> with its <literal>conninfo</literal> string, and
-      <literal>%a</literal> with its node name.
-    </para>
-
-  </refsect1>
-
-</refentry>

doc/repmgr-standby-switchover.xml

@@ -1,449 +0,0 @@
-<refentry id="repmgr-standby-switchover">
-  <indexterm>
-    <primary>repmgr standby switchover</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr standby switchover</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr standby switchover</refname>
-    <refpurpose>promote a standby to primary and demote the existing primary to a standby</refpurpose>
-  </refnamediv>
-
-
-  <refsect1>
-    <title>Description</title>
-
-    <para>
-      Promotes a standby to primary and demotes the existing primary to a standby.
-      This command must be run on the standby to be promoted, and requires a
-      passwordless SSH connection to the current primary.
-    </para>
-    <para>
-      If other nodes are connected to the demotion candidate, &repmgr; can instruct
-      these to follow the new primary if the option <literal>--siblings-follow</literal>
-      is specified. This requires a passwordless SSH connection between the promotion
-      candidate (new primary) and the nodes attached to the demotion candidate
-      (existing primary). Note that a witness server, if in use, is also
-	  counted as a &quot;sibling node&quot; as it needs to be instructed to
-	  synchronise its metadata with the new primary.
-    </para>
-    <note>
-      <para>
-        Performing a switchover is a non-trivial operation. In particular it
-        relies on the current primary being able to shut down cleanly and quickly.
-        &repmgr; will attempt to check for potential issues but cannot guarantee
-        a successful switchover.
-      </para>
-      <para>
-        &repmgr; will refuse to perform the switchover if an exclusive backup is running on
-        the current primary, or if WAL replay is paused on the standby.
-      </para>
-    </note>
-    <para>
-      For more details on performing a switchover, including preparation and configuration,
-      see section <xref linkend="performing-switchover"/>.
-    </para>
-
-    <note>
-      <para>
-        From <link linkend="release-4.2">repmgr 4.2</link>, &repmgr; will instruct any running
-        &repmgrd; instances to pause operations while the switchover
-        is being carried out, to prevent &repmgrd; from
-        unintentionally promoting a node. For more details, see <xref linkend="repmgrd-pausing"/>.
-      </para>
-      <para>
-        Users of &repmgr; versions prior to 4.2 should ensure that &repmgrd;
-        is not running on any nodes while a switchover is being executed.
-      </para>
-    </note>
-
-  </refsect1>
-
-  <refsect1>
-    <title>User permission requirements</title>
-    <para><emphasis>data_directory</emphasis></para>
-    <para>
-      &repmgr; needs to be able to determine the location of the data directory on the
-      demotion candidate. If the &repmgr; is not a superuser or member of the <varname>pg_read_all_settings</varname>
-      <ulink url="https://www.postgresql.org/docs/current/predefined-roles.html">predefined roles</ulink>,
-      the name of a superuser should be provided with the <option>-S</option>/<option>--superuser</option> option.
-    </para>
-    <para><emphasis>CHECKPOINT</emphasis></para>
-    <para>
-      &repmgr; executes <command>CHECKPOINT</command> on the demotion candidate as part of the shutdown
-      process to ensure it shuts down as smoothly as possible.
-    </para>
-    <para>
-      Note that <command>CHECKPOINT</command> requires database superuser permissions to execute.
-      If the <literal>repmgr</literal> user is not a superuser, the name of a superuser should be
-      provided with the <option>-S</option>/<option>--superuser</option> option. From PostgreSQL 15 the <varname>pg_checkpoint</varname>
-      predefined role removes the need for superuser permissions to perform <command>CHECKPOINT</command> command.
-    </para>
-    <para>
-      If &repmgr; is unable to execute the <command>CHECKPOINT</command> command, the switchover
-      can still be carried out, albeit at a greater risk that the demotion candidate may not
-      be able to shut down as smoothly as might otherwise have been the case.
-    </para>
-    <para><emphasis>pg_promote() (PostgreSQL 12 and later)</emphasis></para>
-    <para>
-      From PostgreSQL 12, &repmgr; defaults to using the built-in <command>pg_promote()</command> function to
-      promote a standby to primary.
-    </para>
-    <para>
-      Note that execution of <function>pg_promote()</function> is restricted to superusers or to
-      any user who has been granted execution permission for this function. If the &repmgr; user
-      is not permitted to execute <function>pg_promote()</function>, &repmgr; will fall back to using
-      &quot;<command>pg_ctl promote</command>&quot;. For more details see
-      <link linkend="repmgr-standby-promote">repmgr standby promote</link>.
-    </para>
-  </refsect1>
-
-  <refsect1>
-
-    <title>Options</title>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--always-promote</option></term>
-        <listitem>
-          <para>
-            Promote standby to primary, even if it is behind or has diverged
-            from the original primary. The original primary will be shut down in any case,
-            and will need to be manually reintegrated into the replication cluster.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually execute a switchover.
-          </para>
-          <important>
-            <para>
-              Success of <option>--dry-run</option> does not imply the switchover will
-              complete successfully, only that
-              the prerequisites for performing the operation are met.
-            </para>
-          </important>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>-F</option></term>
-        <term><option>--force</option></term>
-        <listitem>
-          <para>
-            Ignore warnings and continue anyway.
-          </para>
-          <para>
-            Specifically, if a problem is encountered when shutting down the current primary,
-            using <option>-F/--force</option> will cause &repmgr; to continue by promoting
-            the standby to be the new primary, and if <option>--siblings-follow</option> is
-            specified, attach any other standbys to the new primary.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--force-rewind[=/path/to/pg_rewind]</option></term>
-        <listitem>
-          <para>
-            Use <application>pg_rewind</application> to reintegrate the old primary if necessary
-            (and the prerequisites for using <application>pg_rewind</application> are met).
-          </para>
-          <para>
-            If using PostgreSQL 9.4, and the <application>pg_rewind</application>
-            binary is not installed in the PostgreSQL <filename>bin</filename> directory,
-            provide its full path. For more details see also <xref linkend="switchover-pg-rewind"/>
-            and <xref linkend="repmgr-node-rejoin-pg-rewind"/>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>-R</option></term>
-        <term><option>--remote-user</option></term>
-        <listitem>
-          <para>
-            System username for remote SSH operations (defaults to local system user).
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>--repmgrd-no-pause</option></term>
-        <listitem>
-          <para>
-            Don't pause &repmgrd; while executing a switchover.
-          </para>
-          <para>
-            This option should not be used unless you take steps by other means
-            to ensure &repmgrd; is paused or not
-            running on all nodes.
-          </para>
-		  <para>
-            This option cannot be used together with <option>--repmgrd-force-unpause</option>.
-          </para>
-
-        </listitem>
-      </varlistentry>
-
-	  <varlistentry>
-        <term><option>--repmgrd-force-unpause</option></term>
-        <listitem>
-          <para>
-            Always unpause all &repmgrd; instances after executing a switchover. This will ensure that
-			any &repmgrd; instances which were paused before the switchover will be
-			unpaused.
-          </para>
-          <para>
-            This option cannot be used together with <option>--repmgrd-no-pause</option>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-     <varlistentry>
-
-        <term><option>--siblings-follow</option></term>
-        <listitem>
-          <para>
-            Have nodes attached to the old primary follow the new primary.
-          </para>
-          <para>
-            This will also ensure that a witness node, if in use, is updated
-            with the new primary's data.
-          </para>
-          <note>
-            <para>
-              In a future &repmgr; release, <option>--siblings-follow</option> will be applied
-              by default.
-            </para>
-          </note>
-        </listitem>
-      </varlistentry>
-
-     <varlistentry>
-        <term><option>-S</option>/<option>--superuser</option></term>
-        <listitem>
-          <para>
-            Use the named superuser instead of the normal &repmgr; user to perform
-            actions requiring superuser permissions.
-          </para>
-        </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-  </refsect1>
-
-  <refsect1>
-    <title>Configuration file settings</title>
-
-    <para>
-     The following parameters in <filename>repmgr.conf</filename> are relevant to the
-     switchover operation:
-    </para>
-
-    <variablelist>
-
-      <varlistentry>
-        <term><option>replication_lag_critical</option></term>
-        <listitem>
-
-          <indexterm>
-            <primary>replication_lag_critical</primary>
-            <secondary>with &quot;repmgr standby switchover&quot;</secondary>
-          </indexterm>
-
-          <para>
-            If replication lag (in seconds) on the standby exceeds this value, the
-            switchover will be aborted (unless the <literal>-F/--force</literal> option
-            is provided)
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-
-        <term><option>shutdown_check_timeout</option></term>
-        <listitem>
-          <indexterm>
-            <primary>shutdown_check_timeout</primary>
-            <secondary>with &quot;repmgr standby switchover&quot;</secondary>
-          </indexterm>
-
-          <para>
-            The maximum number of seconds to wait for the
-            demotion candidate (current primary) to shut down, before aborting the switchover.
-          </para>
-          <para>
-            Note that this parameter is set on the node where <command>repmgr standby switchover</command>
-            is executed (promotion candidate); setting it on the demotion candidate (former primary) will
-            have no effect.
-          </para>
-         <note>
-           <para>
-             In versions prior to <link linkend="release-4.2">&repmgr; 4.2</link>, <command>repmgr standby switchover</command> would
-             use the values defined in <literal>reconnect_attempts</literal> and <literal>reconnect_interval</literal>
-             to determine the timeout for demotion candidate shutdown.
-           </para>
-         </note>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><option>wal_receive_check_timeout</option></term>
-        <listitem>
-          <indexterm>
-            <primary>wal_receive_check_timeout</primary>
-          <secondary>with &quot;repmgr standby switchover&quot;</secondary>
-          </indexterm>
-
-          <para>
-            After the primary has shut down, the maximum number of seconds to wait for the
-            walreceiver on the standby to flush WAL to disk before comparing WAL receive location
-            with the primary's shut down location.
-         </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-
-        <term><option>standby_reconnect_timeout</option></term>
-        <listitem>
-          <indexterm>
-            <primary>standby_reconnect_timeout</primary>
-            <secondary>with &quot;repmgr standby switchover&quot;</secondary>
-          </indexterm>
-
-          <para>
-            The maximum number of seconds to attempt to wait for the demotion candidate (former primary)
-            to reconnect to the promoted primary (default: 60 seconds)
-          </para>
-          <para>
-            Note that this parameter is set on the node where <command>repmgr standby switchover</command>
-            is executed (promotion candidate); setting it on the demotion candidate (former primary) will
-            have no effect.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-
-        <term><option>node_rejoin_timeout</option></term>
-        <listitem>
-
-          <indexterm>
-            <primary>node_rejoin_timeout</primary>
-            <secondary>with &quot;repmgr standby switchover&quot;</secondary>
-          </indexterm>
-
-          <para>
-            maximum number of seconds to attempt to wait for the demotion candidate (former primary)
-            to reconnect to the promoted primary (default: 60 seconds)
-          </para>
-          <para>
-            Note that this parameter is set on the the demotion candidate (former primary);
-            setting it on the node where <command>repmgr standby switchover</command> is
-            executed will have no effect.
-          </para>
-          <para>
-            However, this value <emphasis>must</emphasis> be less than <option>standby_reconnect_timeout</option> on the
-            promotion candidate (the node where <command>repmgr standby switchover</command> is executed).
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </refsect1>
-
-
-  <refsect1>
-    <title>Execution</title>
-
-    <para>
-      Execute with the <literal>--dry-run</literal> option to test the switchover as far as
-      possible without actually changing the status of either node.
-    </para>
-
-    <para>
-      External database connections, e.g. from an application, should not be permitted while
-      the switchover is taking place. In particular, active transactions on the primary
-      can potentially disrupt the shutdown process.
-    </para>
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-switchover-events">
-    <title>Event notifications</title>
-    <para>
-      <literal>standby_switchover</literal> and <literal>standby_promote</literal>
-      <link linkend="event-notifications">event notifications</link> will be generated for the new primary,
-      and a <literal>node_rejoin</literal> event notification for the former primary (new standby).
-    </para>
-    <para>
-      If using an event notification script, <literal>standby_switchover</literal>
-      will populate the placeholder parameter <literal>%p</literal> with the node ID of
-      the former primary.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Exit codes</title>
-    <para>
-      One of the following exit codes will be emitted by <command>repmgr standby switchover</command>:
-    </para>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>SUCCESS (0)</option></term>
-        <listitem>
-          <para>
-            The switchover completed successfully; or if <option>--dry-run</option> was provided,
-            no issues were detected which would prevent the switchover operation.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_SWITCHOVER_FAIL (18)</option></term>
-        <listitem>
-          <para>
-            The switchover could not be executed.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><option>ERR_SWITCHOVER_INCOMPLETE (22)</option></term>
-        <listitem>
-          <para>
-            The switchover was executed but a problem was encountered.
-            Typically this means the former primary could not be reattached
-            as a standby. Check preceding log messages for more information.
-          </para>
-        </listitem>
-      </varlistentry>
-
-   </variablelist>
-  </refsect1>
-
-  <refsect1>
-    <title>See also</title>
-    <para>
-      <xref linkend="repmgr-standby-follow"/>, <xref linkend="repmgr-node-rejoin"/>
-    </para>
-    <para>
-      For more details on performing a switchover operation, see the section <xref linkend="performing-switchover"/>.
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr-standby-unregister.xml

@@ -1,70 +0,0 @@
-<refentry id="repmgr-standby-unregister">
-  <indexterm>
-    <primary>repmgr standby unregister</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr standby unregister</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr standby unregister</refname>
-    <refpurpose>remove a standby's information from the &repmgr; metadata</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      Unregisters a standby with &repmgr;. This command does not affect the actual
-      replication, just removes the standby's entry from the &repmgr; metadata.
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Execution</title>
-    <para>
-      To unregister a running standby, execute:
-      <programlisting>
-        repmgr standby unregister -f /etc/repmgr.conf</programlisting>
-    </para>
-    <para>
-      This will remove the standby record from &repmgr;'s internal metadata
-      table (<literal>repmgr.nodes</literal>). A <literal>standby_unregister</literal>
-      event notification will be recorded in the <literal>repmgr.events</literal> table.
-    </para>
-    <para>
-      If the standby is not running, the command can be executed on another
-      node by providing the id of the node to be unregistered using
-      the command line parameter <literal>--node-id</literal>, e.g. executing the following
-      command on the primary server will unregister the standby with
-      id <literal>3</literal>:
-      <programlisting>
-        repmgr standby unregister -f /etc/repmgr.conf --node-id=3</programlisting>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Options</title>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--node-id</option></term>
-        <listitem>
-          <para>
-            <varname>node_id</varname> of the node to unregister (optional)
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-  <refsect1 id="repmgr-standby-unregister-events">
-    <title>Event notifications</title>
-    <para>
-      A <literal>standby_unregister</literal> <link linkend="event-notifications">event notification</link> will be generated.
-    </para>
-  </refsect1>
-
-</refentry>
-

doc/repmgr-witness-register.xml

@@ -1,101 +0,0 @@
-<refentry id="repmgr-witness-register">
-  <indexterm>
-    <primary>repmgr witness register</primary>
-    <seealso>witness server</seealso>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr witness register</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr witness register</refname>
-    <refpurpose>add a witness node's information to the &repmgr; metadata</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      <command>repmgr witness register</command> adds a witness server's node
-      record to the &repmgr; metadata, and if necessary initialises the witness
-      node by installing the &repmgr; extension and copying the &repmgr; metadata
-      to the witness server. This command needs to be executed to enable
-      use of the witness server with &repmgrd;.
-    </para>
-    <para>
-      When executing <command>repmgr witness register</command>, database connection
-      information for the cluster primary server must also be provided.
-    </para>
-    <para>
-      In most cases it's only necessary to provide the primary's hostname with
-      the <option>-h</option>/<option>--host</option> option; &repmgr; will
-      automatically use the <varname>user</varname> and <varname>dbname</varname>
-      values defined in the <varname>conninfo</varname> string defined in the
-      witness node's <filename>repmgr.conf</filename>, unless these are explicitly
-      provided as command line options.
-    </para>
-
-    <note>
-      <para>
-        The primary server must be registered with <command><link linkend="repmgr-primary-register">repmgr primary register</link></command> before the witness
-        server can be registered.
-      </para>
-    </note>
-
-    <para>
-      Execute with the <option>--dry-run</option> option to check what would happen
-      without actually registering the witness server.
-    </para>
-  </refsect1>
-  <refsect1>
-    <title>Example</title>
-    <para>
-      <programlisting>
-    $ repmgr -f /etc/repmgr.conf witness register -h node1
-    INFO: connecting to witness node "node3" (ID: 3)
-    INFO: connecting to primary node
-    NOTICE: attempting to install extension "repmgr"
-    NOTICE: "repmgr" extension successfully installed
-    INFO: witness registration complete
-    NOTICE: witness node "node3" (ID: 3) successfully registered
-      </programlisting>
-    </para>
-  </refsect1>
-
-
-
-  <refsect1>
-
-    <title>Options</title>
-   <variablelist>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually register the witness
-          </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-       <term><option>-F</option>/<option>--force</option></term>
-        <listitem>
-          <para>
-            Overwrite an existing node record
-          </para>
-        </listitem>
-      </varlistentry>
-
-   </variablelist>
-  </refsect1>
-
-  <refsect1 id="repmgr-witness-register-events">
-    <title>Event notifications</title>
-    <para>
-      A <literal>witness_register</literal> <link linkend="event-notifications">event notification</link> will be generated.
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr-witness-unregister.xml

@@ -1,102 +0,0 @@
-<refentry id="repmgr-witness-unregister" xreflabel="repmgr witness unregister">
-  <indexterm>
-    <primary>repmgr witness unregister</primary>
-  </indexterm>
-
-  <refmeta>
-    <refentrytitle>repmgr witness unregister</refentrytitle>
-  </refmeta>
-
-  <refnamediv>
-    <refname>repmgr witness unregister</refname>
-    <refpurpose>remove a witness node's information to the &repmgr; metadata</refpurpose>
-  </refnamediv>
-
-  <refsect1>
-    <title>Description</title>
-    <para>
-      <command>repmgr witness unregister</command> removes a witness server's node
-      record from the &repmgr; metadata.
-    </para>
-    <para>
-      The node does not have to be running to be unregistered, however if this is the
-      case then either provide connection information for the primary server, or
-	  execute <command>repmgr witness unregister</command> on a running node and
-	  provide the parameter <option>--node-id</option> with the node ID of the
-	  witness server.
-    </para>
-    <para>
-      Execute with the <literal>--dry-run</literal> option to check what would happen
-      without actually registering the witness server.
-    </para>
-  </refsect1>
-  <refsect1>
-    <title>Examples</title>
-    <para>
-      Unregistering a running witness node:
-      <programlisting>
-    $ repmgr -f /etc/repmgr.conf witness unregister
-    INFO: connecting to witness node "node3" (ID: 3)
-    INFO: unregistering witness node 3
-    INFO: witness unregistration complete
-    DETAIL: witness node with UD 3 successfully unregistered</programlisting>
-    </para>
-    <para>
-      Unregistering a non-running witness node:
-      <programlisting>
-        $ repmgr -f /etc/repmgr.conf witness unregister -h node1 -p 5501  -F
-        INFO: connecting to node "node3" (ID: 3)
-        NOTICE: unable to connect to node "node3" (ID: 3), removing node record on cluster primary only
-        INFO: unregistering witness node 3
-        INFO: witness unregistration complete
-        DETAIL: witness node with id ID 3 successfully unregistered</programlisting>
-    </para>
-  </refsect1>
-
-  <refsect1>
-    <title>Notes</title>
-    <para>
-      This command will not make any changes to the witness node itself and will neither
-      remove any data from the witness database nor stop the PostgreSQL instance.
-    </para>
-    <para>
-      A witness node which has been unregistered, can be re-registered with
-      <link linkend="repmgr-witness-register">repmgr witness register --force</link>.
-    </para>
-  </refsect1>
-
-  <refsect1>
-
-    <title>Options</title>
-    <variablelist>
-
-      <varlistentry>
-        <term><option>--dry-run</option></term>
-        <listitem>
-          <para>
-            Check prerequisites but don't actually unregister the witness.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--node-id</option></term>
-        <listitem>
-          <para>
-            Unregister witness server with the specified node ID.
-          </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </refsect1>
-
-
-  <refsect1 id="repmgr-witness-unregister-events">
-    <title>Event notifications</title>
-    <para>
-      A <literal>witness_unregister</literal> <link linkend="event-notifications">event notification</link> will be generated.
-    </para>
-  </refsect1>
-
-</refentry>

doc/repmgr.xml

@@ -1,132 +0,0 @@
-<!-- doc/repmgr.xml -->
-
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
-          "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
-[
-          <!ENTITY % version SYSTEM "version.xml">
-          %version;
-
-          <!ENTITY % filelist SYSTEM "filelist.xml">
-          %filelist;
-
-          <!ENTITY repmgr "<productname>repmgr</productname>">
-          <!ENTITY repmgrd "<productname>repmgrd</productname>">
-          <!ENTITY postgres "<productname>PostgreSQL</productname>">
-]>
-
-<book id="repmgr">
- <title>repmgr &repmgrversion; Documentation</title>
-
- <bookinfo>
-  <corpauthor>EDB</corpauthor>
-  <productname>repmgr</productname>
-  <productnumber>&repmgrversion;</productnumber>
-  &legal;
-
-  <abstract>
-   <para>
-   This is the official documentation of &repmgr; &repmgrversion; for
-   use with PostgreSQL 12 - PostgreSQL 17.
-   </para>
-   <para>
-     &repmgr; is being continually developed and we strongly recommend using the
-     latest version. Please check the
-     <ulink url="https://repmgr.org/">repmgr website</ulink> for details
-     about the current &repmgr; version as well as the
-     <ulink url="https://repmgr.org/docs/current/index.html">current repmgr documentation</ulink>.
-   </para>
-
-   <para>
-    &repmgr; is developed by
-    <ulink url="https://www.enterprisedb.com/">EDB</ulink>
-    along with contributions from other individuals and organisations.
-    Contributions from the community are appreciated and welcome - get
-    in touch via <ulink url="https://github.com/EnterpriseDB/repmgr">github</ulink>
-    or <ulink url="https://groups.google.com/group/repmgr">the mailing list/forum</ulink>.
-    Multiple EDB customers contribute funding to make &repmgr; development possible.
-   </para>
-
-   <para>
-     &repmgr; is fully supported by EDB's
-     <ulink url="https://www.enterprisedb.com/support/postgresql-support-overview-get-the-most-out-of-postgresql">24/7 Production Support</ulink>.
-     EDB, a Major Sponsor of the PostgreSQL project, continues to maintain &repmgr;.
-     We welcome participation from other organisations and individual developers.
-   </para>
-  </abstract>
-
-  <keywordset>
-   <keyword>repmgr</keyword>
-   <keyword>PostgreSQL</keyword>
-   <keyword>replication</keyword>
-   <keyword>asynchronous</keyword>
-   <keyword>HA</keyword>
-   <keyword>high-availability</keyword>
-  </keywordset>
- </bookinfo>
-
-
- <part id="getting-started">
-  <title>Getting started</title>
-  &overview;
-  &install;
-  &quickstart;
- </part>
-
- <part id="repmgr-administration-manual">
-  <title>repmgr administration manual</title>
-
-  &configuration;
-  &cloning-standbys;
-  &promoting-standby;
-  &follow-new-primary;
-  &switchover;
-  &event-notifications;
-  &upgrading-repmgr;
- </part>
-
- <part id="using-repmgrd">
-  <title>Using repmgrd</title>
-  &repmgrd-overview;
-  &repmgrd-automatic-failover;
-  &repmgrd-configuration;
-  &repmgrd-operation;
- </part>
-
- <part id="repmgr-command-reference">
-  <title>repmgr command reference</title>
-
-  &repmgr-primary-register;
-  &repmgr-primary-unregister;
-  &repmgr-standby-clone;
-  &repmgr-standby-register;
-  &repmgr-standby-unregister;
-  &repmgr-standby-promote;
-  &repmgr-standby-follow;
-  &repmgr-standby-switchover;
-  &repmgr-witness-register;
-  &repmgr-witness-unregister;
-  &repmgr-node-status;
-  &repmgr-node-check;
-  &repmgr-node-rejoin;
-  &repmgr-node-service;
-  &repmgr-cluster-show;
-  &repmgr-cluster-matrix;
-  &repmgr-cluster-crosscheck;
-  &repmgr-cluster-event;
-  &repmgr-cluster-cleanup;
-  &repmgr-service-status;
-  &repmgr-service-pause;
-  &repmgr-service-unpause;
-  &repmgr-daemon-start;
-  &repmgr-daemon-stop;
- </part>
-
- &appendix-release-notes;
- &appendix-signatures;
- &appendix-faq;
- &appendix-packages;
- &appendix-support;
-
- <index id="bookindex"></index>
-
-</book>

doc/repmgrd-automatic-failover.xml

@@ -1,941 +0,0 @@
-<chapter id="repmgrd-automatic-failover" xreflabel="Automatic failover with repmgrd">
-
- <title>Automatic failover with repmgrd</title>
-
- <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>automatic failover</secondary>
- </indexterm>
-
- <para>
-  &repmgrd; is a management and monitoring daemon which runs
-  on each node in a replication cluster. It can automate actions such as
-  failover and updating standbys to follow the new primary, as well as
-  providing monitoring information about the state of each standby.
- </para>
-
- <sect1 id="repmgrd-witness-server" xreflabel="Using a witness server with repmgrd">
-   <title>Using a witness server</title>
-
- <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>witness server</secondary>
- </indexterm>
-
- <indexterm>
-   <primary>witness server</primary>
-   <secondary>repmgrd</secondary>
- </indexterm>
-
- <para>
-   A <xref linkend="witness-server"/> is a normal PostgreSQL instance which
-   is not part of the streaming replication cluster; its purpose is, if a
-   failover situation occurs, to provide proof that it is the primary server
-   itself which is unavailable, rather than e.g. a network split between
-   different physical locations.
- </para>
-
- <para>
-   A typical use case for a witness server is a two-node streaming replication
-   setup, where the primary and standby are in different locations (data centres).
-   By creating a witness server in the same location (data centre) as the primary,
-   if the primary becomes unavailable it's possible for the standby to decide whether
-   it can promote itself without risking a "split brain" scenario: if it can't see either the
-   witness or the primary server, it's likely there's a network-level interruption
-   and it should not promote itself. If it can see the witness but not the primary,
-   this proves there is no network interruption and the primary itself is unavailable,
-   and it can therefore promote itself (and ideally take action to fence the
-   former primary).
- </para>
- <note>
-   <para>
-     <emphasis>Never</emphasis> install a witness server on the same physical host
-     as another node in the replication cluster managed by &repmgr; - it's essential
-     the witness is not affected in any way by failure of another node.
-   </para>
- </note>
- <para>
-   For more complex replication scenarios, e.g. with multiple datacentres, it may
-   be preferable to use location-based failover, which ensures that only nodes
-   in the same location as the primary will ever be promotion candidates;
-   see <xref linkend="repmgrd-network-split"/> for more details.
- </para>
-
- <note>
-   <simpara>
-     A witness server will only be useful if &repmgrd;
-     is in use.
-   </simpara>
- </note>
-
- <sect2 id="creating-witness-server">
-   <title>Creating a witness server</title>
- <para>
-   To create a witness server, set up a normal PostgreSQL instance on a server
-   in the same physical location as the cluster's primary server.
- </para>
- <para>
-   This instance should <emphasis>not</emphasis> be on the same physical host as the primary server,
-   as otherwise if the primary server fails due to hardware issues, the witness
-   server will be lost too.
- </para>
- <note>
-   <simpara>
-     A PostgreSQL instance can only accommodate a single witness server.
-   </simpara>
-   <simpara>
-     If you are planning to use a single server to support more than one
-     witness server, a separate PostgreSQL instance is required for each
-     witness server in use.
-   </simpara>
- </note>
-
- <para>
-   The witness server should be configured in the same way as a normal
-   &repmgr; node; see section <xref linkend="configuration"/>.
- </para>
- <para>
-   Register the witness server with <xref linkend="repmgr-witness-register"/>.
-   This will create the &repmgr; extension on the witness server, and make
-   a copy of the &repmgr; metadata.
- </para>
- <note>
-   <simpara>
-    As the witness server is not part of the replication cluster, further
-    changes to the &repmgr; metadata will be synchronised by
-    &repmgrd;.
-   </simpara>
- </note>
- <para>
-   Once the witness server has been configured, &repmgrd;
-   should be started.
- </para>
-
- <para>
-  To unregister a witness server, use <xref linkend="repmgr-witness-unregister"/>.
- </para>
-
- </sect2>
-
-</sect1>
-
-
-<sect1 id="repmgrd-network-split" xreflabel="Handling network splits with repmgrd">
- <title>Handling network splits with repmgrd</title>
- <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>network splits</secondary>
- </indexterm>
-
- <indexterm>
-   <primary>network splits</primary>
- </indexterm>
-
- <para>
-  A common pattern for replication cluster setups is to spread servers over
-  more than one datacentre. This can provide benefits such as geographically-
-  distributed read replicas and DR (disaster recovery capability). However
-  this also means there is a risk of disconnection at network level between
-  datacentre locations, which would result in a split-brain scenario if
-  servers in a secondary data centre were no longer able to see the primary
-  in the main data centre and promoted a standby among themselves.
- </para>
- <para>
-  &repmgr; enables provision of &quot;<xref linkend="witness-server"/>&quot; to
-  artificially create a quorum of servers in a particular location, ensuring
-  that nodes in another location will not elect a new primary if they
-  are unable to see the majority of nodes. However this approach does not
-  scale well, particularly with more complex replication setups, e.g.
-  where the majority of nodes are located outside of the primary datacentre.
-  It also means the <literal>witness</literal> node needs to be managed as an
-  extra PostgreSQL instance outside of the main replication cluster, which
-  adds administrative and programming complexity.
- </para>
- <para>
-  <literal>repmgr4</literal> introduces the concept of <literal>location</literal>:
-  each node is associated with an arbitrary location string (default is
-  <literal>default</literal>); this is set in <filename>repmgr.conf</filename>, e.g.:
-  <programlisting>
-    node_id=1
-    node_name=node1
-    conninfo='host=node1 user=repmgr dbname=repmgr connect_timeout=2'
-    data_directory='/var/lib/postgresql/data'
-    location='dc1'</programlisting>
- </para>
- <para>
-  In a failover situation, &repmgrd; will check if any servers in the
-  same location as the current primary node are visible.  If not, &repmgrd;
-  will assume a network interruption and not promote any node in any
-  other location (it will however enter <link linkend="repmgrd-degraded-monitoring">degraded monitoring</link>
-  mode until a primary becomes visible).
- </para>
-
-</sect1>
-
-
-<sect1 id="repmgrd-primary-visibility-consensus" xreflabel="Primary visibility consensus">
-  <title>Primary visibility consensus</title>
-
-  <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>primary visibility consensus</secondary>
-  </indexterm>
-
-  <indexterm>
-   <primary>primary_visibility_consensus</primary>
-  </indexterm>
-
-  <para>
-    In more complex replication setups, particularly where replication occurs between
-    multiple datacentres, it's possible that some but not all standbys get cut off from the
-    primary (but not from the other standbys).
-  </para>
-  <para>
-    In this situation, normally it's not desirable for any of the standbys which have been
-    cut off to initiate a failover, as the primary is still functioning and standbys are
-    connected. Beginning with <link linkend="release-4.4">&repmgr; 4.4</link>
-    it is now possible for the affected standbys to build a consensus about whether
-    the primary is still available to some standbys (&quot;primary visibility consensus&quot;).
-    This is done by polling each standby (and the witness, if present) for the time it last saw the
-    primary; if any have seen the primary very recently, it's reasonable
-    to infer that the primary is still available and a failover should not be started.
-  </para>
-
-  <para>
-    The time the primary was last seen by each node can be checked by executing
-    <link linkend="repmgr-service-status"><command>repmgr service status</command></link>
-    (&repmgr; 4.2 - 4.4: <link linkend="repmgr-service-status"><command>repmgr daemon status</command></link>)
-    which includes this in its output, e.g.:
-    <programlisting>$ repmgr -f /etc/repmgr.conf service status
- ID | Name  | Role    | Status    | Upstream | repmgrd | PID   | Paused? | Upstream last seen
-----+-------+---------+-----------+----------+---------+-------+---------+--------------------
- 1  | node1 | primary | * running |          | running | 27259 | no      | n/a
- 2  | node2 | standby |   running | node1    | running | 27272 | no      | 1 second(s) ago
- 3  | node3 | standby |   running | node1    | running | 27282 | no      | 0 second(s) ago
- 4  | node4 | witness | * running | node1    | running | 27298 | no      | 1 second(s) ago</programlisting>
-
-  </para>
-
-  <para>
-    To enable this functionality, in <filename>repmgr.conf</filename> set:
-    <programlisting>
-      primary_visibility_consensus=true</programlisting>
-  </para>
-  <note>
-    <para>
-      <option>primary_visibility_consensus</option> <emphasis>must</emphasis> be set to
-      <literal>true</literal> on all nodes for it to be effective.
-    </para>
-  </note>
-
-  <para>
-    The following sample &repmgrd; log output demonstrates the behaviour in a situation
-    where one of three standbys is no longer able to connect to the primary, but <emphasis>can</emphasis>
-    connect to the two other standbys (&quot;sibling nodes&quot;):
-    <programlisting>
-    [2019-05-17 05:36:12] [WARNING] unable to reconnect to node 1 after 3 attempts
-    [2019-05-17 05:36:12] [INFO] 2 active sibling nodes registered
-    [2019-05-17 05:36:12] [INFO] local node's last receive lsn: 0/7006E58
-    [2019-05-17 05:36:12] [INFO] checking state of sibling node "node3" (ID: 3)
-    [2019-05-17 05:36:12] [INFO] node "node3" (ID: 3) reports its upstream is node 1, last seen 1 second(s) ago
-    [2019-05-17 05:36:12] [NOTICE] node 3 last saw primary node 1 second(s) ago, considering primary still visible
-    [2019-05-17 05:36:12] [INFO] last receive LSN for sibling node "node3" (ID: 3) is: 0/7006E58
-    [2019-05-17 05:36:12] [INFO] node "node3" (ID: 3) has same LSN as current candidate "node2" (ID: 2)
-    [2019-05-17 05:36:12] [INFO] checking state of sibling node "node4" (ID: 4)
-    [2019-05-17 05:36:12] [INFO] node "node4" (ID: 4) reports its upstream is node 1, last seen 0 second(s) ago
-    [2019-05-17 05:36:12] [NOTICE] node 4 last saw primary node 0 second(s) ago, considering primary still visible
-    [2019-05-17 05:36:12] [INFO] last receive LSN for sibling node "node4" (ID: 4) is: 0/7006E58
-    [2019-05-17 05:36:12] [INFO] node "node4" (ID: 4) has same LSN as current candidate "node2" (ID: 2)
-    [2019-05-17 05:36:12] [INFO] 2 nodes can see the primary
-    [2019-05-17 05:36:12] [DETAIL] following nodes can see the primary:
-     - node "node3" (ID: 3): 1 second(s) ago
-     - node "node4" (ID: 4): 0 second(s) ago
-    [2019-05-17 05:36:12] [NOTICE] cancelling failover as some nodes can still see the primary
-    [2019-05-17 05:36:12] [NOTICE] election cancelled
-    [2019-05-17 05:36:14] [INFO] node "node2" (ID: 2) monitoring upstream node "node1" (ID: 1) in degraded state</programlisting>
-    In this situation it will cancel the failover and enter degraded monitoring node,
-    waiting for the primary to reappear.
-  </para>
-</sect1>
-
-<sect1 id="repmgrd-standby-disconnection-on-failover" xreflabel="Standby disconnection on failover">
-  <title>Standby disconnection on failover</title>
-
-  <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>standby disconnection on failover</secondary>
- </indexterm>
-
-  <indexterm>
-    <primary>standby disconnection on failover</primary>
-  </indexterm>
-
-  <para>
-    If <option>standby_disconnect_on_failover</option> is set to <literal>true</literal> in
-    <filename>repmgr.conf</filename>, in a failover situation &repmgrd; will forcibly disconnect
-    the local node's WAL receiver, and wait for the WAL receiver on all sibling nodes to be
-	disconnected, before making a failover decision.
-  </para>
-  <note>
-    <para>
-      <option>standby_disconnect_on_failover</option> is available with PostgreSQL 9.5 and later.
-      Until PostgreSQL 14 this requires that the <literal>repmgr</literal> database user is a superuser.
-      From PostgreSQL 15 a specific ALTER SYSTEM privilege can be granted to the <literal>repmgr</literal> database
-      user with e.g. <command>GRANT ALTER SYSTEM ON PARAMETER wal_retrieve_retry_interval TO repmgr</command>.
-    </para>
-  </note>
-  <para>
-    By doing this, it's possible to ensure that, at the point the failover decision is made, no nodes
-    are receiving data from the primary and their LSN location will be static.
-  </para>
-  <important>
-    <para>
-      <option>standby_disconnect_on_failover</option> <emphasis>must</emphasis> be set to the same value on
-      all nodes.
-    </para>
-  </important>
-  <para>
-    Note that when using <option>standby_disconnect_on_failover</option> there will be a delay of 5 seconds
-    plus however many seconds it takes to confirm the WAL receiver is disconnected before
-    &repmgrd; proceeds with the failover decision.
-  </para>
-  <para>
-	&repmgrd; will wait up to <option>sibling_nodes_disconnect_timeout</option> seconds (default:
-	<literal>30</literal>) to confirm that the WAL receiver on all sibling nodes hase been
-	disconnected before proceding with the failover operation. If the timeout is reached, the
-	failover operation will go ahead anyway.
-  </para>
-  <para>
-    Following the failover operation, no matter what the outcome, each node will reconnect its WAL receiver.
-  </para>
-  <para>
-    If using <option>standby_disconnect_on_failover</option>, we recommend that the
-    <option>primary_visibility_consensus</option> option is also used.
-  </para>
-
-</sect1>
-
-<sect1 id="repmgrd-failover-validation" xreflabel="Failover validation">
-  <title>Failover validation</title>
-
-  <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>failover validation</secondary>
- </indexterm>
-
-  <indexterm>
-    <primary>failover validation</primary>
-  </indexterm>
-
-  <para>
-    From <link linkend="release-4.3">repmgr 4.3</link>, &repmgr; makes it possible to provide a script
-    to &repmgrd; which, in a failover situation,
-    will be executed by the promotion candidate (the node which has been selected
-    to be the new primary) to confirm whether the node should actually be promoted.
-  </para>
-  <para>
-    To use this, <option>failover_validation_command</option> in <filename>repmgr.conf</filename>
-    to a script executable by the <literal>postgres</literal> system user, e.g.:
-    <programlisting>
-      failover_validation_command=/path/to/script.sh %n</programlisting>
-  </para>
-  <para>
-    The <literal>%n</literal> parameter will be replaced with the node ID when the script is
-    executed. A number of other parameters are also available, see section
-    &quot;<xref linkend="repmgrd-automatic-failover-configuration-optional"/>&quot; for details.
-  </para>
-  <para>
-    This script must return an exit code of <literal>0</literal> to indicate the node should promote itself.
-    Any other value will result in the promotion being aborted and the election rerun.
-    There is a pause of <option>election_rerun_interval</option> seconds before the election is rerun.
-  </para>
-  <para>
-    Sample &repmgrd; log file output during which the failover validation
-    script rejects the proposed promotion candidate:
-    <programlisting>
-[2019-03-13 21:01:30] [INFO] visible nodes: 2; total nodes: 2; no nodes have seen the primary within the last 4 seconds
-[2019-03-13 21:01:30] [NOTICE] promotion candidate is "node2" (ID: 2)
-[2019-03-13 21:01:30] [NOTICE] executing "failover_validation_command"
-[2019-03-13 21:01:30] [DETAIL] /usr/local/bin/failover-validation.sh 2
-[2019-03-13 21:01:30] [INFO] output returned by failover validation command:
-Node ID: 2
-
-[2019-03-13 21:01:30] [NOTICE] failover validation command returned a non-zero value: "1"
-[2019-03-13 21:01:30] [NOTICE] promotion candidate election will be rerun
-[2019-03-13 21:01:30] [INFO] 1 followers to notify
-[2019-03-13 21:01:30] [NOTICE] notifying node "node3" (ID: 3) to rerun promotion candidate selection
-INFO:  node 3 received notification to rerun promotion candidate election
-[2019-03-13 21:01:30] [NOTICE] rerunning election after 15 seconds ("election_rerun_interval")</programlisting>
-  </para>
-
-
-</sect1>
-
- <sect1 id="cascading-replication" xreflabel="Cascading replication">
-  <title>repmgrd and cascading replication</title>
-
-  <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>cascading replication</secondary>
-  </indexterm>
-
- <indexterm>
-   <primary>cascading replication</primary>
-   <secondary>repmgrd</secondary>
- </indexterm>
-
- <para>
-  Cascading replication - where a standby can connect to an upstream node and not
-  the primary server itself - was introduced in PostgreSQL 9.2. &repmgr; and
-  &repmgrd; support cascading replication by keeping track of the relationship
-  between standby servers - each node record is stored with the node id of its
-  upstream ("parent") server (except of course the primary server).
- </para>
- <para>
-  In a failover situation where the primary node fails and a top-level standby
-  is promoted, a standby connected to another standby will not be affected
-  and continue working as normal (even if the upstream standby it's connected
-  to becomes the primary node). If however the node's direct upstream fails,
-  the &quot;cascaded standby&quot; will attempt to reconnect to that node's parent
-  (unless <varname>failover</varname> is set to <literal>manual</literal> in
-  <filename>repmgr.conf</filename>).
- </para>
-
-  </sect1>
-
-<sect1 id="repmgrd-primary-child-disconnection" xreflabel="Monitoring standby disconnections on the primary">
-  <title>Monitoring standby disconnections on the primary node</title>
-
-  <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>standby disconnection</secondary>
-  </indexterm>
-
-  <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>child node disconnection</secondary>
-  </indexterm>
-
-  <note>
-    <para>
-      This functionality is available in <link linkend="release-4.4">&repmgr; 4.4</link> and later.
-    </para>
-  </note>
-  <para>
-    When running on the primary node, &repmgrd; can
-    monitor connections and in particular disconnections by its attached
-    child nodes (standbys, and if in use, the witness server), and optionally
-    execute a custom command if certain criteria are met (such as the number of
-    attached nodes falling to zero following a failover to a new primary); this
-    command can be used for example to &quot;fence&quot; the node and ensure it
-    is isolated from any applications attempting to access the replication cluster.
-  </para>
-
-  <note>
-	<para>
-	  Currently &repmgrd; can only detect disconnections
-	  of streaming replication standbys and cannot determine whether a standby
-	  has disconnected and fallen back to archive recovery.
-	</para>
-	<para>
-	  See section <link linkend="repmgrd-primary-child-disconnection-caveats">caveats</link> below.
-	</para>
-  </note>
-
-  <sect2 id="repmgrd-primary-child-disconnection-monitoring-process">
-	<title>Standby disconnections monitoring process and criteria</title>
-	<para>
-	  &repmgrd; monitors attached child nodes and decides
-	  whether to invoke the user-defined command based on the following process
-	  and criteria:
-    <itemizedlist>
-
-      <listitem>
-        <para>
-          Every few seconds (defined by the configuration parameter <varname>child_nodes_check_interval</varname>;
-          default: <literal>5</literal> seconds, a value of <literal>0</literal> disables this altogether), &repmgrd; queries
-          the <literal>pg_stat_replication</literal> system view and compares
-          the nodes present there against the list of nodes registered with &repmgr; which
-          should be attached to the primary.
-        </para>
-        <para>
-          If a witness server is in use, &repmgrd; connects to it and checks which upstream node
-          it is following.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If a child node (standby) is no longer present in <literal>pg_stat_replication</literal>,
-          &repmgrd; notes the time it detected the node's absence, and additionally generates a
-          <literal>child_node_disconnect</literal> event.
-        </para>
-        <para>
-          If a witness server is in use, and it is no longer following the primary, or not
-          reachable at all, &repmgrd; notes the time it detected the node's absence, and additionally generates a
-          <literal>child_node_disconnect</literal> event.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If a child node (standby) which was absent from <literal>pg_stat_replication</literal> reappears,
-          &repmgrd; clears the time it detected the node's absence, and additionally generates a
-          <literal>child_node_reconnect</literal> event.
-        </para>
-        <para>
-          If a witness server is in use, which was previously not reachable or not following the
-          primary node, has become reachable and is following the primary node,  &repmgrd; clears the
-          time it detected the node's absence, and additionally generates a
-          <literal>child_node_reconnect</literal> event.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If an entirely new child node (standby or witness) is detected, &repmgrd; adds it to its internal list
-          and additionally generates a <literal>child_node_new_connect</literal> event.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          If the <varname>child_nodes_disconnect_command</varname> parameter is set in
-          <filename>repmgr.conf</filename>, &repmgrd; will then loop through all child nodes.
-          If it determines that insufficient child nodes are connected, and a
-          minimum of <varname>child_nodes_disconnect_timeout</varname> seconds (default: <literal>30</literal>)
-          has elapsed since  the last node became disconnected, &repmgrd; will then execute the
-          <varname>child_nodes_disconnect_command</varname> script.
-        </para>
-        <para>
-          By default, the <varname>child_nodes_disconnect_command</varname> will only be executed
-          if all child nodes are disconnected. If <varname>child_nodes_connected_min_count</varname>
-          is set, the <varname>child_nodes_disconnect_command</varname> script will be triggered
-          if the number of connected child nodes falls below the specified value (e.g.
-          if set to <literal>2</literal>, the script will be triggered if only one child node
-          is connected). Alternatively, if <varname>child_nodes_disconnect_min_count</varname>
-          and more than that number of child nodes disconnects, the script will be triggered.
-        </para>
-        <note>
-          <para>
-            By default, a witness node, if in use, will <emphasis>not</emphasis> be counted as a
-            child node for the purposes of determining whether to execute
-            <varname>child_nodes_disconnect_command</varname>.
-          </para>
-          <para>
-            To enable the witness node to be counted as a child node, set
-            <varname>child_nodes_connected_include_witness</varname> in <filename>repmgr.conf</filename>
-            to <literal>true</literal>
-            (and <link linkend="repmgrd-reloading-configuration">reload the configuration</link> if &repmgrd;
-            is running).
-          </para>
-        </note>
-      </listitem>
-
-      <listitem>
-        <para>
-          Note that child nodes which are not attached when &repmgrd;
-          starts will <emphasis>not</emphasis> be considered as missing, as &repmgrd;
-          cannot know why they are not attached.
-        </para>
-      </listitem>
-
-    </itemizedlist>
-	</para>
-  </sect2>
-
-  <sect2 id="repmgrd-primary-child-disconnection-example">
-	<title>Standby disconnections monitoring process example</title>
-	<para>
-	  This example shows typical &repmgrd; log output from a three-node cluster
-	  (primary and two child nodes), with <varname>child_nodes_connected_min_count</varname>
-	  set to <literal>2</literal>.
-	</para>
-	<para>
-	  &repmgrd; on the primary has started up, while two child
-	  nodes are being provisioned:
-	  <programlisting>
-[2019-04-24 15:25:33] [INFO] monitoring primary node "node1" (ID: 1) in normal state
-[2019-04-24 15:25:35] [NOTICE] new node "node2" (ID: 2) has connected
-[2019-04-24 15:25:35] [NOTICE] 1 (of 1) child nodes are connected, but at least 2 child nodes required
-[2019-04-24 15:25:35] [INFO] no child nodes have detached since repmgrd startup
-(...)
-[2019-04-24 15:25:44] [NOTICE] new node "node3" (ID: 3) has connected
-[2019-04-24 15:25:46] [INFO] monitoring primary node "node1" (ID: 1) in normal state
-(...)</programlisting>
-	</para>
-	<para>
-	  One of the child nodes has disconnected; &repmgrd;
-	  is now waiting <varname>child_nodes_disconnect_timeout</varname> seconds
-	  before executing <varname>child_nodes_disconnect_command</varname>:
-	  <programlisting>
-[2019-04-24 15:28:11] [INFO] monitoring primary node "node1" (ID: 1) in normal state
-[2019-04-24 15:28:17] [INFO] monitoring primary node "node1" (ID: 1) in normal state
-[2019-04-24 15:28:19] [NOTICE] node "node3" (ID: 3) has disconnected
-[2019-04-24 15:28:19] [NOTICE] 1 (of 2) child nodes are connected, but at least 2 child nodes required
-[2019-04-24 15:28:19] [INFO] most recently detached child node was 3 (ca. 0 seconds ago), not triggering "child_nodes_disconnect_command"
-[2019-04-24 15:28:19] [DETAIL] "child_nodes_disconnect_timeout" set To 30 seconds
-(...)</programlisting>
-	</para>
-	<para>
-	  <varname>child_nodes_disconnect_command</varname> is executed once:
-	  <programlisting>
-[2019-04-24 15:28:49] [INFO] most recently detached child node was 3 (ca. 30 seconds ago), triggering "child_nodes_disconnect_command"
-[2019-04-24 15:28:49] [INFO] "child_nodes_disconnect_command" is:
-	"/usr/bin/fence-all-the-things.sh"
-[2019-04-24 15:28:51] [NOTICE] 1 (of 2) child nodes are connected, but at least 2 child nodes required
-[2019-04-24 15:28:51] [INFO] "child_nodes_disconnect_command" was previously executed, taking no action</programlisting>
-	</para>
-
-  </sect2>
-
-  <sect2 id="repmgrd-primary-child-disconnection-caveats">
-	<title>Standby disconnections monitoring caveats</title>
-	<para>
-	  The following caveats should be considered if you are intending to use this functionality.
-	</para>
-	<para>
-	  <itemizedlist mark="bullet">
-		<listitem>
-          <para>
-			If a child node is configured to use archive recovery, it's possible that
-			the child node will disconnect from the primary node and fall back to
-			archive recovery. In this case &repmgrd;
-			will nevertheless register a node disconnection.
-		  </para>
-		</listitem>
-
-        <listitem>
-          <para>
-			&repmgr; relies on <varname>application_name</varname> in the child node's
-			<varname>primary_conninfo</varname> string to be the same as the node name
-			defined in the node's <filename>repmgr.conf</filename> file. Furthermore,
-			this <varname>application_name</varname> must be unique across the replication
-			cluster.
-          </para>
-		  <para>
-			If a custom <varname>application_name</varname> is used, or the
-			<varname>application_name</varname> is not unique across the replication
-			cluster, &repmgr; will not be able to reliably monitor child node connections.
-		  </para>
-        </listitem>
-
-	  </itemizedlist>
-	</para>
-  </sect2>
-
-
-  <sect2 id="repmgrd-primary-child-disconnection-configuration">
-	<title>Standby disconnections monitoring process configuration</title>
-	<para>
-	  The following parameters, set in <filename>repmgr.conf</filename>,
-	  control how child node disconnection monitoring operates.
-	</para>
-	<variablelist>
-
-      <varlistentry>
-        <term><varname>child_nodes_check_interval</varname></term>
-        <listitem>
-          <indexterm>
-		    <primary>child_nodes_check_interval</primary>
-		    <secondary>child node disconnection monitoring</secondary>
-		  </indexterm>
-
-		  <para>
-			Interval (in seconds) after which &repmgrd; queries the
-			<literal>pg_stat_replication</literal> system view and compares the nodes present
-			there against the list of nodes registered with repmgr which should be attached to the primary.
-		  </para>
-		  <para>
-			Default is <literal>5</literal> seconds, a value of <literal>0</literal> disables this check
-			altogether.
-		  </para>
-		</listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-        <term><varname>child_nodes_disconnect_command</varname></term>
-
-        <listitem>
-          <indexterm>
-		    <primary>child_nodes_disconnect_command</primary>
-		    <secondary>child node disconnection monitoring</secondary>
-		  </indexterm>
-
-		  <para>
-			User-definable script to be executed when &repmgrd;
-			determines that an insufficient number of child nodes are connected. By default
-			the script is executed when no child nodes are executed, but the execution
-			threshold can be modified by setting one of <varname>child_nodes_connected_min_count</varname>
-			or<varname>child_nodes_disconnect_min_count</varname> (see below).
-		  </para>
-		  <para>
-			The <varname>child_nodes_disconnect_command</varname> script can be
-			any user-defined script or program. It <emphasis>must</emphasis> be able
-			to be executed by the system user under which the PostgreSQL server itself
-			runs (usually <literal>postgres</literal>).
-		  </para>
-		  <note>
-			<para>
-			  If <varname>child_nodes_disconnect_command</varname> is not set, no action
-			  will be taken.
-			</para>
-		  </note>
-		  <para>
-			If specified, the following format placeholder will be substituted when
-			executing <varname>child_nodes_disconnect_command</varname>:
-		  </para>
-
-		   <variablelist>
-			 <varlistentry>
-			   <term><option>%p</option></term>
-			   <listitem>
-				 <para>
-				   ID of the node executing the <varname>child_nodes_disconnect_command</varname> script.
-				 </para>
-			   </listitem>
-			 </varlistentry>
-		   </variablelist>
-
-		  <para>
-			The <varname>child_nodes_disconnect_command</varname> script will only be executed once
-			while the criteria for its execution are met. If the criteria for its execution are no longer
-			met (i.e. some child nodes have reconnected), it will be executed again if
-			the criteria for its execution are met again.
-          </para>
-          <para>
-			The <varname>child_nodes_disconnect_command</varname> script will not be executed if
-			&repmgrd; is <link linkend="repmgrd-pausing">paused</link>.
-          </para>
-
-		</listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-        <term><varname>child_nodes_disconnect_timeout</varname></term>
-
-        <listitem>
-          <indexterm>
-		    <primary>child_nodes_disconnect_timeout</primary>
-		    <secondary>child node disconnection monitoring</secondary>
-		  </indexterm>
-
-		  <para>
-			If &repmgrd; determines that an insufficient number of
-			child nodes are connected, it will wait for the specified number of seconds
-			to execute the <varname>child_nodes_disconnect_command</varname>.
-		  </para>
-		  <para>
-			Default: <literal>30</literal> seconds.
-		  </para>
-		</listitem>
-	  </varlistentry>
-
-      <varlistentry>
-        <term><varname>child_nodes_connected_min_count</varname></term>
-        <listitem>
-          <indexterm>
-		    <primary>child_nodes_connected_min_count</primary>
-		    <secondary>child node disconnection monitoring</secondary>
-		  </indexterm>
-
-		  <para>
-			If the number of child nodes connected falls below the number specified in
-			this parameter, the <varname>child_nodes_disconnect_command</varname> script
-			will be executed.
-		  </para>
-		  <para>
-			For example, if <varname>child_nodes_connected_min_count</varname> is set
-			to <literal>2</literal>, the <varname>child_nodes_disconnect_command</varname>
-			script will be executed if one or no child nodes are connected.
-		  </para>
-		  <para>
-			Note that <varname>child_nodes_connected_min_count</varname> overrides any value
-			set in <varname>child_nodes_disconnect_min_count</varname>.
-		  </para>
-		  <para>
-			If neither of <varname>child_nodes_connected_min_count</varname> or
-			<varname>child_nodes_disconnect_min_count</varname> are set,
-			the <varname>child_nodes_disconnect_command</varname> script
-			will be executed when no child nodes are connected.
-		  </para>
-          <para>
-            A witness node, if in use, will not be counted as a child node unless
-            <varname>child_nodes_connected_include_witness</varname> is set to <literal>true</literal>.
-          </para>
-		</listitem>
-	  </varlistentry>
-
-
-	  <varlistentry>
-        <term><varname>child_nodes_disconnect_min_count</varname></term>
-        <listitem>
-          <indexterm>
-		    <primary>child_nodes_disconnect_min_count</primary>
-		    <secondary>child node disconnection monitoring</secondary>
-		  </indexterm>
-
-		  <para>
-			If the number of disconnected child nodes exceeds the number specified in
-			this parameter, the <varname>child_nodes_disconnect_command</varname> script
-			will be executed.
-		  </para>
-
-		  <para>
-			For example, if <varname>child_nodes_disconnect_min_count</varname> is set
-			to <literal>2</literal>, the <varname>child_nodes_disconnect_command</varname>
-			script will be executed if more than two child nodes are disconnected.
-		  </para>
-
-		  <para>
-			Note that any value set in <varname>child_nodes_disconnect_min_count</varname>
-			will be overriden by <varname>child_nodes_connected_min_count</varname>.
-		  </para>
-		  <para>
-			If neither of <varname>child_nodes_connected_min_count</varname> or
-			<varname>child_nodes_disconnect_min_count</varname> are set,
-			the <varname>child_nodes_disconnect_command</varname> script
-			will be executed when no child nodes are connected.
-		  </para>
-
-          <para>
-            A witness node, if in use, will not be counted as a child node unless
-            <varname>child_nodes_connected_include_witness</varname> is set to <literal>true</literal>.
-          </para>
-
-		</listitem>
-	  </varlistentry>
-
-
-	  <varlistentry>
-        <term><varname>child_nodes_connected_include_witness</varname></term>
-        <listitem>
-          <indexterm>
-		    <primary>child_nodes_connected_include_witness</primary>
-		    <secondary>child node disconnection monitoring</secondary>
-		  </indexterm>
-
-		  <para>
-            Whether to count the witness node (if in use) as a child node when
-            determining whether to execute <varname>child_nodes_disconnect_command</varname>.
-          </para>
-          <para>
-            Default to <literal>false</literal>.
-          </para>
-        </listitem>
-      </varlistentry>
-
-	</variablelist>
-
-  </sect2>
-
-  <sect2 id="repmgrd-primary-child-disconnection-events">
-	<title>Standby disconnections monitoring process event notifications</title>
-	<para>
-	  The following <link linkend="event-notifications">event notifications</link> may be generated:
-	</para>
-	<variablelist>
-
-      <varlistentry>
-        <term><varname>child_node_disconnect</varname></term>
-        <listitem>
-          <indexterm>
-		    <primary>child_node_disconnect</primary>
-		    <secondary>event notification</secondary>
-		  </indexterm>
-
-          <para>
-			This event is generated after &repmgrd;
-			detects that a child node is no longer streaming from the primary node.
-          </para>
-		  <para>
-			Example:
-			<programlisting>
-$ repmgr cluster event --event=child_node_disconnect
- Node ID | Name  | Event                 | OK | Timestamp           | Details
----------+-------+-----------------------+----+---------------------+--------------------------------------------
- 1       | node1 | child_node_disconnect | t  | 2019-04-24 12:41:36 | node "node3" (ID: 3) has disconnected</programlisting>
-		  </para>
-        </listitem>
-      </varlistentry>
-
-	  <varlistentry>
-        <term><varname>child_node_reconnect</varname></term>
-        <listitem>
-          <indexterm>
-		    <primary>child_node_reconnect</primary>
-		    <secondary>event notification</secondary>
-		  </indexterm>
-
-          <para>
-			This event is generated after &repmgrd;
-			detects that a child node has resumed streaming from the primary node.
-          </para>
-		  <para>
-			Example:
-			<programlisting>
-$ repmgr cluster event --event=child_node_reconnect
- Node ID | Name  | Event                | OK | Timestamp           | Details
----------+-------+----------------------+----+---------------------+------------------------------------------------------------
- 1       | node1 | child_node_reconnect | t  | 2019-04-24 12:42:19 | node "node3" (ID: 3) has reconnected after 42 seconds</programlisting>
-		  </para>
-        </listitem>
-      </varlistentry>
-
-	  <varlistentry>
-        <term><varname>child_node_new_connect</varname></term>
-        <listitem>
-          <indexterm>
-		    <primary>child_node_new_connect</primary>
-		    <secondary>event notification</secondary>
-		  </indexterm>
-
-          <para>
-			This event is generated after &repmgrd;
-			detects that a new child node has been registered with &repmgr; and has
-			connected to the primary.
-          </para>
-		  <para>
-			Example:
-			<programlisting>
-$ repmgr cluster event --event=child_node_new_connect
- Node ID | Name  | Event                  | OK | Timestamp           | Details
----------+-------+------------------------+----+---------------------+---------------------------------------------
- 1       | node1 | child_node_new_connect | t  | 2019-04-24 12:41:30 | new node "node3" (ID: 3) has connected</programlisting>
-		  </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><varname>child_nodes_disconnect_command</varname></term>
-        <listitem>
-          <indexterm>
-		    <primary>child_nodes_disconnect_command</primary>
-		    <secondary>event notification</secondary>
-		  </indexterm>
-
-          <para>
-			This event is generated after &repmgrd; detects
-			that sufficient child nodes have been disconnected for a sufficient amount
-			of time to trigger execution of the <varname>child_nodes_disconnect_command</varname>.
-          </para>
-		  <para>
-			Example:
-			<programlisting>
-$ repmgr cluster event --event=child_nodes_disconnect_command
- Node ID | Name  | Event                          | OK | Timestamp           | Details
----------+-------+--------------------------------+----+---------------------+--------------------------------------------------------
- 1       | node1 | child_nodes_disconnect_command | t  | 2019-04-24 13:08:17 | "child_nodes_disconnect_command" successfully executed</programlisting>
-		  </para>
-        </listitem>
-      </varlistentry>
-
-	</variablelist>
-
-  </sect2>
-
-
-</sect1>
-
-
-</chapter>

doc/repmgrd-node-fencing.md

@@ -108,7 +108,7 @@ The actual script is as follows; adjust the configurable items as appropriate:
 
     # 1. Promote this node from standby to primary
 
-    repmgr standby promote -f /etc/repmgr.conf --log-to-file
+    repmgr standby promote -f /etc/repmgr.conf
 
     # 2. Reconfigure pgbouncer instances
 
@@ -146,7 +146,7 @@ Script and template file should be installed on each node where `repmgrd` is run
 Finally, set `promote_command` in `repmgr.conf` on each node to
 point to the custom promote script:
 
-    promote_command='/var/lib/postgres/repmgr/promote.sh'
+    promote_command=/var/lib/postgres/repmgr/promote.sh
 
 and reload/restart any running `repmgrd` instances for the changes to take
 effect.

doc/repmgrd-operation.xml

@@ -1,401 +0,0 @@
-<chapter id="repmgrd-operation" xreflabel="repmgrd operation">
-  <title>repmgrd operation</title>
-
-  <indexterm>
-    <primary>repmgrd</primary>
-    <secondary>operation</secondary>
-  </indexterm>
-
-  <sect1 id="repmgrd-pausing" xreflabel="pausing the repmgrd service">
-
-    <title>Pausing the repmgrd service</title>
-
-  <indexterm>
-    <primary>repmgrd</primary>
-    <secondary>pausing</secondary>
-  </indexterm>
-
-  <indexterm>
-    <primary>pausing repmgrd</primary>
-  </indexterm>
-
-
-  <para>
-    In normal operation, &repmgrd; monitors the state of the
-    PostgreSQL node it is running on, and will take appropriate action if problems
-    are detected, e.g. (if so configured) promote the node to primary, if the existing
-    primary has been determined as failed.
-  </para>
-
-  <para>
-    However, &repmgrd; is unable to distinguish between
-    planned outages (such as performing a <link linkend="performing-switchover">switchover</link>
-    or installing PostgreSQL maintenance released), and an actual server outage. In versions prior to
-    &repmgr; 4.2 it was necessary to stop &repmgrd; on all nodes (or at least
-    on all nodes where &repmgrd; is
-    <link linkend="repmgrd-automatic-failover">configured for automatic failover</link>)
-    to prevent &repmgrd; from making unintentional changes to the
-    replication cluster.
-  </para>
-
-  <para>
-    From <link linkend="release-4.2">&repmgr; 4.2</link>, &repmgrd;
-    can now be &quot;paused&quot;, i.e. instructed not to take any action such as performing a failover.
-    This can be done from any node in the cluster, removing the need to stop/restart
-    each &repmgrd; individually.
-  </para>
-
-  <note>
-    <para>
-      For major PostgreSQL upgrades, e.g. from PostgreSQL 11 to PostgreSQL 12,
-      &repmgrd; should be shut down completely and only started up
-      once the &repmgr; packages for the new PostgreSQL major version have been installed.
-    </para>
-  </note>
-
-  <sect2 id="repmgrd-pausing-prerequisites">
-    <title>Prerequisites for pausing &repmgrd;</title>
-    <para>
-      In order to be able to pause/unpause &repmgrd;, following
-      prerequisites must be met:
-      <itemizedlist spacing="compact" mark="bullet">
-
-        <listitem>
-          <simpara><link linkend="release-4.2">&repmgr; 4.2</link> or later must be installed on all nodes.</simpara>
-        </listitem>
-
-        <listitem>
-          <simpara>The same major &repmgr; version (e.g. 4.2) must be installed on all nodes (and preferably the same minor version).</simpara>
-        </listitem>
-
-        <listitem>
-          <simpara>
-            PostgreSQL on all nodes must be accessible from the node where the
-            <literal>pause</literal>/<literal>unpause</literal> operation is executed, using the
-            <varname>conninfo</varname> string shown by <link linkend="repmgr-cluster-show"><command>repmgr cluster show</command></link>.
-          </simpara>
-        </listitem>
-      </itemizedlist>
-    </para>
-    <note>
-      <para>
-        These conditions are required for normal &repmgr; operation in any case.
-      </para>
-    </note>
-
-  </sect2>
-
-  <sect2 id="repmgrd-pausing-execution">
-    <title>Pausing/unpausing &repmgrd;</title>
-    <para>
-      To pause &repmgrd;, execute <link linkend="repmgr-service-pause"><command>repmgr service pause</command></link>
-      (&repmgr; 4.2 - 4.4: <link linkend="repmgr-service-pause"><command>repmgr daemon pause</command></link>),
-      e.g.:
-   <programlisting>
-$ repmgr -f /etc/repmgr.conf service pause
-NOTICE: node 1 (node1) paused
-NOTICE: node 2 (node2) paused
-NOTICE: node 3 (node3) paused</programlisting>
-    </para>
-    <para>
-      The state of &repmgrd; on each node can be checked with
-      <link linkend="repmgr-service-status"><command>repmgr service status</command></link>
-      (&repmgr; 4.2 - 4.4: <link linkend="repmgr-service-status"><command>repmgr daemon status</command></link>),
-      e.g.:
-    <programlisting>$ repmgr -f /etc/repmgr.conf service status
- ID | Name  | Role    | Status  | repmgrd | PID  | Paused?
-----+-------+---------+---------+---------+------+---------
- 1  | node1 | primary | running | running | 7851 | yes
- 2  | node2 | standby | running | running | 7889 | yes
- 3  | node3 | standby | running | running | 7918 | yes</programlisting>
-    </para>
-
-    <note>
-      <para>
-        If executing a switchover with <link linkend="repmgr-standby-switchover"><command>repmgr standby switchover</command></link>,
-	&repmgr; will automatically pause/unpause the &repmgrd; service as part of the switchover process.
-      </para>
-    </note>
-
-    <para>
-      If the primary (in this example, <literal>node1</literal>) is stopped, &repmgrd;
-      running on one of the standbys (here: <literal>node2</literal>) will react like this:
-      <programlisting>
-[2019-08-28 12:22:21] [WARNING] unable to connect to upstream node "node1" (node ID: 1)
-[2019-08-28 12:22:21] [INFO] checking state of node 1, 1 of 5 attempts
-[2019-08-28 12:22:21] [INFO] sleeping 1 seconds until next reconnection attempt
-...
-[2019-08-28 12:22:24] [INFO] sleeping 1 seconds until next reconnection attempt
-[2019-08-28 12:22:25] [INFO] checking state of node 1, 5 of 5 attempts
-[2019-08-28 12:22:25] [WARNING] unable to reconnect to node 1 after 5 attempts
-[2019-08-28 12:22:25] [NOTICE] node is paused
-[2019-08-28 12:22:33] [INFO] node "node2" (ID: 2) monitoring upstream node "node1" (node ID: 1) in degraded state
-[2019-08-28 12:22:33] [DETAIL] repmgrd paused by administrator
-[2019-08-28 12:22:33] [HINT] execute "repmgr service unpause" to resume normal failover mode</programlisting>
-    </para>
-    <para>
-      If the primary becomes available again (e.g. following a software upgrade), &repmgrd;
-      will automatically reconnect, e.g.:
-      <programlisting>
-[2019-08-28 12:25:41] [NOTICE] reconnected to upstream node "node1" (ID: 1) after 8 seconds, resuming monitoring</programlisting>
-    </para>
-
-    <para>
-      To unpause the &repmgrd; service, execute
-      <link linkend="repmgr-service-unpause"><command>repmgr service unpause</command></link>
-      ((&repmgr; 4.2 - 4.4: <link linkend="repmgr-service-unpause"><command>repmgr daemon unpause</command></link>),
-      e.g.:
-   <programlisting>
-$ repmgr -f /etc/repmgr.conf service unpause
-NOTICE: node 1 (node1) unpaused
-NOTICE: node 2 (node2) unpaused
-NOTICE: node 3 (node3) unpaused</programlisting>
-    </para>
-
-    <note>
-      <para>
-        If the previous primary is no longer accessible when &repmgrd;
-        is unpaused, no failover action will be taken. Instead, a new primary must be manually promoted using
-        <link linkend="repmgr-standby-promote"><command>repmgr standby promote</command></link>,
-	and any standbys attached to the new primary with
-	<link linkend="repmgr-standby-follow"><command>repmgr standby follow</command></link>.
-      </para>
-      <para>
-        This is to prevent execution of <link linkend="repmgr-service-unpause"><command>repmgr service unpause</command></link>
-        resulting in the automatic promotion of a new primary, which may be a problem particularly
-        in larger clusters, where &repmgrd; could select a different promotion
-        candidate to the one intended by the administrator.
-      </para>
-    </note>
-  </sect2>
-  <sect2 id="repmgrd-pausing-details">
-    <title>Details on the &repmgrd; pausing mechanism</title>
-
-    <para>
-      The pause state of each node will be stored over a PostgreSQL restart.
-    </para>
-
-    <para>
-      <link linkend="repmgr-service-pause"><command>repmgr service pause</command></link> and
-      <link linkend="repmgr-service-unpause"><command>repmgr service unpause</command></link> can be
-      executed even if &repmgrd; is not running; in this case,
-      &repmgrd; will start up in whichever pause state has been set.
-    </para>
-    <note>
-      <para>
-	    <link linkend="repmgr-service-pause"><command>repmgr service pause</command></link> and
-	    <link linkend="repmgr-service-unpause"><command>repmgr service unpause</command></link>
-	    <emphasis>do not</emphasis> start/stop &repmgrd;.
-      </para>
-      <para>
-        The commands <link linkend="repmgr-daemon-start"><command>repmgr daemon start</command></link>
-        and <link linkend="repmgr-daemon-stop"><command>repmgr daemon stop</command></link>
-        (<link linkend="repmgrd-service-configuration">if correctly configured</link>) can be used to start/stop
-        &repmgrd; on individual nodes.
-      </para>
-    </note>
-  </sect2>
-  </sect1>
-
-  <sect1 id="repmgrd-wal-replay-pause">
-    <title>repmgrd and paused WAL replay</title>
-
-    <indexterm>
-      <primary>repmgrd</primary>
-      <secondary>paused WAL replay</secondary>
-    </indexterm>
-
-    <para>
-      If WAL replay has been paused (using <command>pg_wal_replay_pause()</command>,
-      on PostgreSQL 9.6 and earlier <command>pg_xlog_replay_pause()</command>),
-      in a failover situation &repmgrd; will
-      automatically resume WAL replay.
-    </para>
-    <para>
-      This is because if WAL replay is paused, but WAL is pending replay,
-      PostgreSQL cannot be promoted until WAL replay is resumed.
-    </para>
-    <note>
-      <para>
-        <command><link linkend="repmgr-standby-promote">repmgr standby promote</link></command>
-        will refuse to promote a node in this state, as the PostgreSQL
-        <command>promote</command> command will not be acted on until
-        WAL replay is resumed, leaving the cluster in a potentially
-        unstable state. In this case it is up to the user to
-        decide whether to resume WAL replay.
-      </para>
-    </note>
-  </sect1>
-
-<sect1 id="repmgrd-degraded-monitoring" xreflabel="repmgrd degraded monitoring">
- <title>"degraded monitoring" mode</title>
-
- <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>degraded monitoring</secondary>
- </indexterm>
-
- <indexterm>
-   <primary>degraded monitoring</primary>
- </indexterm>
-
- <para>
-  In certain circumstances, &repmgrd; is not able to fulfill its primary mission
-  of monitoring the node's upstream server. In these cases it enters &quot;degraded monitoring&quot;
-  mode, where &repmgrd; remains active but is waiting for the situation
-  to be resolved.
- </para>
- <para>
-  Situations where this happens are:
-  <itemizedlist spacing="compact" mark="bullet">
-
-   <listitem>
-    <simpara>a failover situation has occurred, no nodes in the primary node's location are visible</simpara>
-   </listitem>
-
-   <listitem>
-    <simpara>a failover situation has occurred, but no promotion candidate is available</simpara>
-   </listitem>
-
-   <listitem>
-    <simpara>a failover situation has occurred, but the promotion candidate could not be promoted</simpara>
-   </listitem>
-
-   <listitem>
-    <simpara>a failover situation has occurred, but the node was unable to follow the new primary</simpara>
-   </listitem>
-
-   <listitem>
-    <simpara>a failover situation has occurred, but no primary has become available</simpara>
-   </listitem>
-
-   <listitem>
-    <simpara>a failover situation has occurred, but automatic failover is not enabled for the node</simpara>
-   </listitem>
-
-   <listitem>
-    <simpara>repmgrd is monitoring the primary node, but it is not available (and no other node has been promoted as primary)</simpara>
-   </listitem>
-  </itemizedlist>
- </para>
-
- <para>
-  Example output in a situation where there is only one standby with <literal>failover=manual</literal>,
-  and the primary node is unavailable (but is later restarted):
-  <programlisting>
-    [2017-08-29 10:59:19] [INFO] node "node2" (ID: 2) monitoring upstream node "node1" (ID: 1) in normal state (automatic failover disabled)
-    [2017-08-29 10:59:33] [WARNING] unable to connect to upstream node "node1" (ID: 1)
-    [2017-08-29 10:59:33] [INFO] checking state of node 1, 1 of 5 attempts
-    [2017-08-29 10:59:33] [INFO] sleeping 1 seconds until next reconnection attempt
-    (...)
-    [2017-08-29 10:59:37] [INFO] checking state of node 1, 5 of 5 attempts
-    [2017-08-29 10:59:37] [WARNING] unable to reconnect to node 1 after 5 attempts
-    [2017-08-29 10:59:37] [NOTICE] this node is not configured for automatic failover so will not be considered as promotion candidate
-    [2017-08-29 10:59:37] [NOTICE] no other nodes are available as promotion candidate
-    [2017-08-29 10:59:37] [HINT] use "repmgr standby promote" to manually promote this node
-    [2017-08-29 10:59:37] [INFO] node "node2" (ID: 2) monitoring upstream node "node1" (ID: 1) in degraded state (automatic failover disabled)
-    [2017-08-29 10:59:53] [INFO] node "node2" (ID: 2) monitoring upstream node "node1" (ID: 1) in degraded state (automatic failover disabled)
-    [2017-08-29 11:00:45] [NOTICE] reconnected to upstream node "node1" (ID: 1) after 68 seconds, resuming monitoring
-    [2017-08-29 11:00:57] [INFO] node "node2" (ID: 2) monitoring upstream node "node1" (ID: 1) in normal state (automatic failover disabled)</programlisting>
-
- </para>
- <para>
-  By default, <literal>repmgrd</literal> will continue in degraded monitoring mode indefinitely.
-  However a timeout (in seconds) can be set with <varname>degraded_monitoring_timeout</varname>,
-  after which &repmgrd; will terminate.
- </para>
-
- <note>
-   <para>
-     If &repmgrd; is monitoring a primary mode which has been stopped
-     and manually restarted as a standby attached to a new primary, it will automatically detect
-     the status change and update the node record to reflect the node's new status
-     as an active standby. It will then resume monitoring the node as a standby.
-   </para>
- </note>
-</sect1>
-
-
-<sect1 id="repmgrd-monitoring" xreflabel="Storing monitoring data">
- <title>Storing monitoring data</title>
- <indexterm>
-   <primary>repmgrd</primary>
-   <secondary>monitoring</secondary>
- </indexterm>
- <indexterm>
-   <primary>monitoring</primary>
-   <secondary>with repmgrd</secondary>
- </indexterm>
-
- <para>
-   When &repmgrd; is running with the option <literal>monitoring_history=true</literal>,
-  it will constantly write standby node status information to the
-  <varname>monitoring_history</varname> table, providing a near-real time
-  overview of replication status on all nodes
-  in the cluster.
- </para>
- <para>
-   The view <literal>replication_status</literal> shows the most recent state
-   for each node, e.g.:
-  <programlisting>
-    repmgr=# select * from repmgr.replication_status;
-    -[ RECORD 1 ]-------------+------------------------------
-    primary_node_id           | 1
-    standby_node_id           | 2
-    standby_name              | node2
-    node_type                 | standby
-    active                    | t
-    last_monitor_time         | 2017-08-24 16:28:41.260478+09
-    last_wal_primary_location | 0/6D57A00
-    last_wal_standby_location | 0/5000000
-    replication_lag           | 29 MB
-    replication_time_lag      | 00:00:11.736163
-    apply_lag                 | 15 MB
-    communication_time_lag    | 00:00:01.365643</programlisting>
- </para>
- <para>
-  The interval in which monitoring history is written is controlled by the
-  configuration parameter <varname>monitor_interval_secs</varname>;
-  default is 2.
- </para>
- <para>
-  As this can generate a large amount of monitoring data in the table
-  <literal>repmgr.monitoring_history</literal>. it's advisable to regularly
-  purge historical data using the <xref linkend="repmgr-cluster-cleanup"/>
-  command; use the <literal>-k/--keep-history</literal> option to
-  specify how many day's worth of data should be retained.
- </para>
- <para>
-  It's possible to use &repmgrd; to run in monitoring
-  mode only (without automatic failover capability) for some or all
-  nodes by setting <literal>failover=manual</literal> in the node's
-  <filename>repmgr.conf</filename> file. In the event of the node's upstream failing,
-  no failover action will be taken and the node will require manual intervention to
-  be reattached to replication. If this occurs, an
-  <link linkend="event-notifications">event notification</link>
-  <varname>standby_disconnect_manual</varname> will be created.
- </para>
- <para>
-  Note that when a standby node is not streaming directly from its upstream
-  node, e.g. recovering WAL from an archive, <varname>apply_lag</varname> will always appear as
-  <literal>0 bytes</literal>.
- </para>
- <tip>
-  <para>
-   If monitoring history is enabled, the contents of the <literal>repmgr.monitoring_history</literal>
-   table will be replicated to attached standbys. This means there will be a small but
-   constant stream of replication activity which may not be desirable. To prevent
-   this, convert the table to an <literal>UNLOGGED</literal> one with:
-   <programlisting>
-     ALTER TABLE repmgr.monitoring_history SET UNLOGGED;</programlisting>
-  </para>
-  <para>
-   This will however mean that monitoring history will not be available on
-   another node following a failover, and the view <literal>repmgr.replication_status</literal>
-   will not work on standbys.
-  </para>
- </tip>
-</sect1>
-
-
-</chapter>

doc/repmgrd-overview.xml

@@ -1,187 +0,0 @@
-<chapter id="repmgrd-overview" xreflabel="repmgrd overview">
-  <title>repmgrd overview</title>
-
-  <indexterm>
-    <primary>repmgrd</primary>
-    <secondary>overview</secondary>
-  </indexterm>
-
-  <para>
-    &repmgrd; (&quot;<literal>replication manager daemon</literal>&quot;)
-    is a management and monitoring daemon which runs
-    on each node in a replication cluster. It can automate actions such as
-    failover and updating standbys to follow the new primary, as well as
-    providing monitoring information about the state of each standby.
-  </para>
-  <para>
-    &repmgrd; is designed to be straightforward to set up
-    and does not require additional external infrastructure.
-  </para>
-  <para>
-    Functionality provided by &repmgrd; includes:
-    <itemizedlist spacing="compact" mark="bullet">
-
-       <listitem>
-         <simpara>
-           wide range of <link linkend="repmgrd-basic-configuration">configuration options</link>
-         </simpara>
-       </listitem>
-
-       <listitem>
-         <simpara>
-           option to execute custom scripts (&quot;<link linkend="event-notifications">event notifications</link>&quot;)
-           at different points in the failover sequence
-         </simpara>
-       </listitem>
-
-       <listitem>
-         <simpara>
-           ability to <link linkend="repmgrd-pausing">pause repmgrd</link>
-           operation on all nodes with a
-           <link linkend="repmgr-service-pause"><command>single command</command></link>
-         </simpara>
-       </listitem>
-
-       <listitem>
-         <simpara>
-           optional <link linkend="repmgrd-witness-server">witness server</link>
-         </simpara>
-       </listitem>
-
-       <listitem>
-         <simpara>
-           &quot;location&quot; configuration option to restrict
-           potential promotion candidates to a single location
-           (e.g. when nodes are spread over multiple data centres)
-         </simpara>
-       </listitem>
-
-       <listitem>
-         <simpara>
-           <link linkend="connection-check-type">choice of method</link> to determine node availability
-           (PostgreSQL ping, query execution or new connection)
-         </simpara>
-       </listitem>
-
-       <listitem>
-         <simpara>
-           retention of monitoring statistics (optional)
-         </simpara>
-       </listitem>
-
-
-    </itemizedlist>
-
-  </para>
-
-  <sect1 id="repmgrd-demonstration">
-
-    <title>repmgrd demonstration</title>
-    <para>
-  To demonstrate automatic failover, set up a 3-node replication cluster (one primary
-  and two standbys streaming directly from the primary) so that the cluster looks
-  something like this:
-  <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster show --compact
-     ID | Name  | Role    | Status    | Upstream | Location | Prio.
-    ----+-------+---------+-----------+----------+----------+-------
-     1  | node1 | primary | * running |          | default  | 100
-     2  | node2 | standby |   running | node1    | default  | 100
-     3  | node3 | standby |   running | node1    | default  | 100</programlisting>
- </para>
-
- <tip>
-   <para>
-     See section <link linkend="repmgrd-automatic-failover-configuration">Required configuration for automatic failover</link>
-     for an example of minimal <filename>repmgr.conf</filename> file settings suitable for use with &repmgrd;.
-   </para>
- </tip>
- <para>
-  Start &repmgrd; on each standby and verify that it's running by examining the
-  log output, which at log level <literal>INFO</literal> will look like this:
-  <programlisting>
-    [2019-08-15 07:14:42] [NOTICE] repmgrd (repmgrd 5.0) starting up
-    [2019-08-15 07:14:42] [INFO] connecting to database "host=node2 dbname=repmgr user=repmgr connect_timeout=2"
-    INFO:  set_repmgrd_pid(): provided pidfile is /var/run/repmgr/repmgrd-12.pid
-    [2019-08-15 07:14:42] [NOTICE] starting monitoring of node "node2" (ID: 2)
-    [2019-08-15 07:14:42] [INFO] monitoring connection to upstream node "node1" (ID: 1)</programlisting>
- </para>
- <para>
-  Each &repmgrd; should also have recorded its successful startup as an event:
-  <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster event --event=repmgrd_start
-     Node ID | Name  | Event         | OK | Timestamp           | Details
-    ---------+-------+---------------+----+---------------------+--------------------------------------------------------
-     3       | node3 | repmgrd_start | t  | 2019-08-15 07:14:42 | monitoring connection to upstream node "node1" (ID: 1)
-     2       | node2 | repmgrd_start | t  | 2019-08-15 07:14:41 | monitoring connection to upstream node "node1" (ID: 1)
-     1       | node1 | repmgrd_start | t  | 2019-08-15 07:14:39 | monitoring cluster primary "node1" (ID: 1)</programlisting>
- </para>
- <para>
-  Now stop the current primary server with e.g.:
-  <programlisting>
-    pg_ctl -D /var/lib/postgresql/data -m immediate stop</programlisting>
- </para>
- <para>
-  This will force the primary to shut down straight away, aborting all processes
-  and transactions.  This will cause a flurry of activity in the &repmgrd; log
-  files as each &repmgrd; detects the failure of the primary and a failover
-  decision is made. This is an extract from the log of a standby server (<literal>node2</literal>)
-  which has promoted to new primary after failure of the original primary (<literal>node1</literal>).
-  <programlisting>
-    [2019-08-15 07:27:50] [WARNING] unable to connect to upstream node "node1" (ID: 1)
-    [2019-08-15 07:27:50] [INFO] checking state of node 1, 1 of 3 attempts
-    [2019-08-15 07:27:50] [INFO] sleeping 5 seconds until next reconnection attempt
-    [2019-08-15 07:27:55] [INFO] checking state of node 1, 2 of 3 attempts
-    [2019-08-15 07:27:55] [INFO] sleeping 5 seconds until next reconnection attempt
-    [2019-08-15 07:28:00] [INFO] checking state of node 1, 3 of 3 attempts
-    [2019-08-15 07:28:00] [WARNING] unable to reconnect to node 1 after 3 attempts
-    [2019-08-15 07:28:00] [INFO] primary and this node have the same location ("default")
-    [2019-08-15 07:28:00] [INFO] local node's last receive lsn: 0/900CBF8
-    [2019-08-15 07:28:00] [INFO] node 3 last saw primary node 12 second(s) ago
-    [2019-08-15 07:28:00] [INFO] last receive LSN for sibling node "node3" (ID: 3) is: 0/900CBF8
-    [2019-08-15 07:28:00] [INFO] node "node3" (ID: 3) has same LSN as current candidate "node2" (ID: 2)
-    [2019-08-15 07:28:00] [INFO] visible nodes: 2; total nodes: 2; no nodes have seen the primary within the last 4 seconds
-    [2019-08-15 07:28:00] [NOTICE] promotion candidate is "node2" (ID: 2)
-    [2019-08-15 07:28:00] [NOTICE] this node is the winner, will now promote itself and inform other nodes
-    [2019-08-15 07:28:00] [INFO] promote_command is:
-      "/usr/pgsql-12/bin/repmgr -f /etc/repmgr/12/repmgr.conf standby promote"
-    NOTICE: promoting standby to primary
-    DETAIL: promoting server "node2" (ID: 2) using "/usr/pgsql-12/bin/pg_ctl  -w -D '/var/lib/pgsql/12/data' promote"
-    NOTICE: waiting up to 60 seconds (parameter "promote_check_timeout") for promotion to complete
-    NOTICE: STANDBY PROMOTE successful
-    DETAIL: server "node2" (ID: 2) was successfully promoted to primary
-    [2019-08-15 07:28:01] [INFO] 3 followers to notify
-    [2019-08-15 07:28:01] [NOTICE] notifying node "node3" (ID: 3) to follow node 2
-    INFO:  node 3 received notification to follow node 2
-    [2019-08-15 07:28:01] [INFO] switching to primary monitoring mode
-    [2019-08-15 07:28:01] [NOTICE] monitoring cluster primary "node2" (ID: 2)</programlisting>
- </para>
- <para>
-  The cluster status will now look like this, with the original primary (<literal>node1</literal>)
-  marked as inactive, and standby <literal>node3</literal> now following the new primary
-  (<literal>node2</literal>):
-  <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster show --compact
-     ID | Name  | Role    | Status    | Upstream | Location | Prio.
-    ----+-------+---------+-----------+----------+----------+-------
-     1  | node1 | primary | - failed  |          | default  | 100
-     2  | node2 | primary | * running |          | default  | 100
-     3  | node3 | standby |   running | node2    | default  | 100</programlisting>
-
- </para>
- <para>
-   <link linkend="repmgr-cluster-event"><command>repmgr cluster event</command></link> will display a summary of
-   what happened to each server during the failover:
-  <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster event
-     Node ID | Name  | Event                      | OK | Timestamp           | Details
-    ---------+-------+----------------------------+----+---------------------+-------------------------------------------------------------
-     3       | node3 | repmgrd_failover_follow    | t  | 2019-08-15 07:38:03 | node 3 now following new upstream node 2
-     3       | node3 | standby_follow             | t  | 2019-08-15 07:38:02 | standby attached to upstream node "node2" (ID: 2)
-     2       | node2 | repmgrd_reload             | t  | 2019-08-15 07:38:01 | monitoring cluster primary "node2" (ID: 2)
-     2       | node2 | repmgrd_failover_promote   | t  | 2019-08-15 07:38:01 | node 2 promoted to primary; old primary 1 marked as failed
-     2       | node2 | standby_promote            | t  | 2019-08-15 07:38:01 | server "node2" (ID: 2) was successfully promoted to primary</programlisting>
- </para>
-
-  </sect1>
-</chapter>

doc/stylesheet-common.xsl

@@ -1,89 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                version="1.0">
-
-<!--
-  This file contains XSLT stylesheet customizations that are common to
-  all output formats (HTML, HTML Help, XSL-FO, etc.).
-  -->
-
-<xsl:include href="stylesheet-speedup-common.xsl" />
-
-<!-- Parameters -->
-
-<!--
-<xsl:param name="draft.mode">
-  <xsl:choose>
-    <xsl:when test="contains($repmgr.version, 'devel')">yes</xsl:when>
-    <xsl:otherwise>no</xsl:otherwise>
-  </xsl:choose>
-</xsl:param>
--->
-
-<xsl:param name="show.comments">
-  <xsl:choose>
-    <xsl:when test="contains($repmgr.version, 'devel')">1</xsl:when>
-    <xsl:otherwise>0</xsl:otherwise>
-  </xsl:choose>
-</xsl:param>
-
-<xsl:param name="callout.graphics" select="'0'"></xsl:param>
-<xsl:param name="toc.section.depth">2</xsl:param>
-<xsl:param name="linenumbering.extension" select="'0'"></xsl:param>
-<xsl:param name="section.autolabel" select="1"></xsl:param>
-<xsl:param name="section.label.includes.component.label" select="1"></xsl:param>
-<xsl:param name="refentry.generate.name" select="0"></xsl:param>
-<xsl:param name="refentry.generate.title" select="1"></xsl:param>
-<xsl:param name="refentry.xref.manvolnum" select="0"/>
-<xsl:param name="formal.procedures" select="0"></xsl:param>
-<xsl:param name="generate.consistent.ids" select="1"/>
-<xsl:param name="punct.honorific" select="''"></xsl:param>
-<xsl:param name="variablelist.term.break.after">1</xsl:param>
-<xsl:param name="variablelist.term.separator"></xsl:param>
-<xsl:param name="xref.with.number.and.title" select="0"></xsl:param>
-
-
-<!-- Change display of some elements -->
-
-<xsl:template match="productname">
-  <xsl:call-template name="inline.charseq"/>
-</xsl:template>
-
-<xsl:template match="structfield">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="structname">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="symbol">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="systemitem">
-  <xsl:call-template name="inline.charseq"/>
-</xsl:template>
-
-<xsl:template match="token">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="type">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="programlisting/emphasis">
-  <xsl:call-template name="inline.boldseq"/>
-</xsl:template>
-
-
-<!-- Special support for Tcl synopses -->
-
-<xsl:template match="optional[@role='tcl']">
-  <xsl:text>?</xsl:text>
-  <xsl:call-template name="inline.charseq"/>
-  <xsl:text>?</xsl:text>
-</xsl:template>
-
-</xsl:stylesheet>

doc/stylesheet-fo.xsl

@@ -1,97 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                version="1.0"
-                xmlns:fo="http://www.w3.org/1999/XSL/Format">
-
-<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/fo/docbook.xsl"/>
-<xsl:include href="stylesheet-common.xsl" />
-
-<xsl:param name="fop1.extensions" select="1"></xsl:param>
-<xsl:param name="tablecolumns.extension" select="0"></xsl:param>
-<xsl:param name="toc.max.depth">3</xsl:param>
-<xsl:param name="ulink.footnotes" select="1"></xsl:param>
-<xsl:param name="use.extensions" select="1"></xsl:param>
-<xsl:param name="variablelist.as.blocks" select="1"></xsl:param>
-
-<xsl:attribute-set name="monospace.verbatim.properties"
-                   use-attribute-sets="verbatim.properties monospace.properties">
-  <xsl:attribute name="wrap-option">wrap</xsl:attribute>
-</xsl:attribute-set>
-
-<xsl:attribute-set name="nongraphical.admonition.properties">
-  <xsl:attribute name="border-style">solid</xsl:attribute>
-  <xsl:attribute name="border-width">1pt</xsl:attribute>
-  <xsl:attribute name="border-color">black</xsl:attribute>
-  <xsl:attribute name="padding-start">12pt</xsl:attribute>
-  <xsl:attribute name="padding-end">12pt</xsl:attribute>
-  <xsl:attribute name="padding-top">6pt</xsl:attribute>
-  <xsl:attribute name="padding-bottom">6pt</xsl:attribute>
-</xsl:attribute-set>
-
-<xsl:attribute-set name="admonition.title.properties">
-  <xsl:attribute name="text-align">center</xsl:attribute>
-</xsl:attribute-set>
-
-<!-- fix missing space after vertical simplelist
-     https://github.com/docbook/xslt10-stylesheets/issues/31 -->
-<xsl:attribute-set name="normal.para.spacing">
-  <xsl:attribute name="space-after.optimum">1em</xsl:attribute>
-  <xsl:attribute name="space-after.minimum">0.8em</xsl:attribute>
-  <xsl:attribute name="space-after.maximum">1.2em</xsl:attribute>
-</xsl:attribute-set>
-
-<!-- Change display of some elements -->
-
-<xsl:template match="command">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="confgroup" mode="bibliography.mode">
-  <fo:inline>
-    <xsl:apply-templates select="conftitle/text()" mode="bibliography.mode"/>
-    <xsl:text>, </xsl:text>
-    <xsl:apply-templates select="confdates/text()" mode="bibliography.mode"/>
-    <xsl:value-of select="$biblioentry.item.separator"/>
-  </fo:inline>
-</xsl:template>
-
-<xsl:template match="isbn" mode="bibliography.mode">
-  <fo:inline>
-    <xsl:text>ISBN </xsl:text>
-    <xsl:apply-templates mode="bibliography.mode"/>
-    <xsl:value-of select="$biblioentry.item.separator"/>
-  </fo:inline>
-</xsl:template>
-
-<!-- bug fix from <https://sourceforge.net/p/docbook/bugs/1360/#831b> -->
-
-<xsl:template match="varlistentry/term" mode="xref-to">
-  <xsl:param name="verbose" select="1"/>
-  <xsl:apply-templates mode="no.anchor.mode"/>
-</xsl:template>
-
-<!-- include refsects in PDF bookmarks
-     (https://github.com/docbook/xslt10-stylesheets/issues/46) -->
-
-<xsl:template match="refsect1|refsect2|refsect3"
-              mode="bookmark">
-
-  <xsl:variable name="id">
-    <xsl:call-template name="object.id"/>
-  </xsl:variable>
-  <xsl:variable name="bookmark-label">
-    <xsl:apply-templates select="." mode="object.title.markup"/>
-  </xsl:variable>
-
-  <fo:bookmark internal-destination="{$id}">
-    <xsl:attribute name="starting-state">
-      <xsl:value-of select="$bookmarks.state"/>
-    </xsl:attribute>
-    <fo:bookmark-title>
-      <xsl:value-of select="normalize-space($bookmark-label)"/>
-    </fo:bookmark-title>
-    <xsl:apply-templates select="*" mode="bookmark"/>
-  </fo:bookmark>
-</xsl:template>
-
-</xsl:stylesheet>

doc/stylesheet-html-common.xsl

@@ -1,292 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE xsl:stylesheet [
-<!ENTITY % common.entities SYSTEM "http://docbook.sourceforge.net/release/xsl/current/common/entities.ent">
-%common.entities;
-]>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                version="1.0">
-
-<!--
-  This file contains XSLT stylesheet customizations that are common to
-  all HTML output variants (chunked and single-page).
-  -->
-
-<!-- Parameters -->
-<xsl:param name="make.valid.html" select="1"></xsl:param>
-<xsl:param name="generate.id.attributes" select="1"></xsl:param>
-<xsl:param name="make.graphic.viewport" select="0"/>
-<xsl:param name="link.mailto.url">pgsql-docs@lists.postgresql.org</xsl:param>
-<xsl:param name="toc.max.depth">2</xsl:param>
-
-
-<!-- Change display of some elements -->
-
-<xsl:template match="command">
-  <xsl:call-template name="inline.monoseq"/>
-</xsl:template>
-
-<xsl:template match="confgroup" mode="bibliography.mode">
-  <span>
-    <xsl:call-template name="common.html.attributes"/>
-    <xsl:call-template name="id.attribute"/>
-    <xsl:apply-templates select="conftitle/text()" mode="bibliography.mode"/>
-    <xsl:text>, </xsl:text>
-    <xsl:apply-templates select="confdates/text()" mode="bibliography.mode"/>
-    <xsl:copy-of select="$biblioentry.item.separator"/>
-  </span>
-</xsl:template>
-
-<xsl:template match="isbn" mode="bibliography.mode">
-  <span>
-    <xsl:call-template name="common.html.attributes"/>
-    <xsl:call-template name="id.attribute"/>
-    <xsl:text>ISBN </xsl:text>
-    <xsl:apply-templates mode="bibliography.mode"/>
-    <xsl:copy-of select="$biblioentry.item.separator"/>
-  </span>
-</xsl:template>
-
-
-<!-- table of contents configuration -->
-
-<xsl:param name="generate.toc">
-appendix  toc,title
-article/appendix  nop
-article   toc,title
-book      toc,title
-chapter   toc,title
-part      toc,title
-preface   toc,title
-qandadiv  toc
-qandaset  toc
-reference toc,title
-sect1     toc
-sect2     toc
-sect3     toc
-sect4     toc
-sect5     toc
-section   toc
-set       toc,title
-</xsl:param>
-
-<xsl:param name="generate.section.toc.level" select="1"></xsl:param>
-
-<!-- include refentry under sect1 in tocs -->
-<xsl:template match="sect1" mode="toc">
-  <xsl:param name="toc-context" select="."/>
-  <xsl:call-template name="subtoc">
-    <xsl:with-param name="toc-context" select="$toc-context"/>
-    <xsl:with-param name="nodes" select="sect2|refentry
-                                         |bridgehead[$bridgehead.in.toc != 0]"/>
-  </xsl:call-template>
-</xsl:template>
-
-
-<!-- Put index "quicklinks" (A | B | C | ...) at the top of the bookindex page. -->
-
-<!-- from html/autoidx.xsl -->
-
-<xsl:template name="generate-basic-index">
-  <xsl:param name="scope" select="NOTANODE"/>
-
-  <xsl:variable name="role">
-    <xsl:if test="$index.on.role != 0">
-      <xsl:value-of select="@role"/>
-    </xsl:if>
-  </xsl:variable>
-
-  <xsl:variable name="type">
-    <xsl:if test="$index.on.type != 0">
-      <xsl:value-of select="@type"/>
-    </xsl:if>
-  </xsl:variable>
-
-  <xsl:variable name="terms"
-                select="//indexterm
-                        [count(.|key('letter',
-                          translate(substring(&primary;, 1, 1),
-                             &lowercase;,
-                             &uppercase;))
-                          [&scope;][1]) = 1
-                          and not(@class = 'endofrange')]"/>
-
-  <xsl:variable name="alphabetical"
-                select="$terms[contains(concat(&lowercase;, &uppercase;),
-                                        substring(&primary;, 1, 1))]"/>
-
-  <xsl:variable name="others" select="$terms[not(contains(concat(&lowercase;,
-                                                 &uppercase;),
-                                             substring(&primary;, 1, 1)))]"/>
-
-  <div class="index">
-    <!-- pgsql-docs: begin added stuff -->
-    <p class="indexdiv-quicklinks">
-      <a href="#indexdiv-Symbols">
-        <xsl:call-template name="gentext">
-          <xsl:with-param name="key" select="'index symbols'"/>
-        </xsl:call-template>
-      </a>
-      <xsl:apply-templates select="$alphabetical[count(.|key('letter',
-                                   translate(substring(&primary;, 1, 1),
-                                   &lowercase;,&uppercase;))[&scope;][1]) = 1]"
-                           mode="index-div-quicklinks">
-        <xsl:with-param name="position" select="position()"/>
-        <xsl:with-param name="scope" select="$scope"/>
-        <xsl:with-param name="role" select="$role"/>
-        <xsl:with-param name="type" select="$type"/>
-        <xsl:sort select="translate(&primary;, &lowercase;, &uppercase;)"/>
-      </xsl:apply-templates>
-    </p>
-    <!-- pgsql-docs: end added stuff -->
-
-    <xsl:if test="$others">
-      <xsl:choose>
-        <xsl:when test="normalize-space($type) != '' and
-                        $others[@type = $type][count(.|key('primary', &primary;)[&scope;][1]) = 1]">
-          <!-- pgsql-docs: added id attribute here for linking to it -->
-          <div class="indexdiv" id="indexdiv-Symbols">
-            <h3>
-              <xsl:call-template name="gentext">
-                <xsl:with-param name="key" select="'index symbols'"/>
-              </xsl:call-template>
-            </h3>
-            <dl>
-              <xsl:apply-templates select="$others[count(.|key('primary', &primary;)[&scope;][1]) = 1]"
-                                   mode="index-symbol-div">
-                <xsl:with-param name="position" select="position()"/>
-                <xsl:with-param name="scope" select="$scope"/>
-                <xsl:with-param name="role" select="$role"/>
-                <xsl:with-param name="type" select="$type"/>
-                <xsl:sort select="translate(&primary;, &lowercase;, &uppercase;)"/>
-              </xsl:apply-templates>
-            </dl>
-          </div>
-        </xsl:when>
-        <xsl:when test="normalize-space($type) != ''">
-          <!-- Output nothing, as there isn't a match for $other using this $type -->
-        </xsl:when>
-        <xsl:otherwise>
-          <!-- pgsql-docs: added id attribute here for linking to it -->
-          <div class="indexdiv" id="indexdiv-Symbols">
-            <h3>
-              <xsl:call-template name="gentext">
-                <xsl:with-param name="key" select="'index symbols'"/>
-              </xsl:call-template>
-            </h3>
-            <dl>
-              <xsl:apply-templates select="$others[count(.|key('primary',
-                                          &primary;)[&scope;][1]) = 1]"
-                                  mode="index-symbol-div">
-                <xsl:with-param name="position" select="position()"/>
-                <xsl:with-param name="scope" select="$scope"/>
-                <xsl:with-param name="role" select="$role"/>
-                <xsl:with-param name="type" select="$type"/>
-                <xsl:sort select="translate(&primary;, &lowercase;, &uppercase;)"/>
-              </xsl:apply-templates>
-            </dl>
-          </div>
-        </xsl:otherwise>
-      </xsl:choose>
-    </xsl:if>
-
-    <xsl:apply-templates select="$alphabetical[count(.|key('letter',
-                                 translate(substring(&primary;, 1, 1),
-                                           &lowercase;,&uppercase;))[&scope;][1]) = 1]"
-                         mode="index-div-basic">
-      <xsl:with-param name="position" select="position()"/>
-      <xsl:with-param name="scope" select="$scope"/>
-      <xsl:with-param name="role" select="$role"/>
-      <xsl:with-param name="type" select="$type"/>
-      <xsl:sort select="translate(&primary;, &lowercase;, &uppercase;)"/>
-    </xsl:apply-templates>
-  </div>
-</xsl:template>
-
-<xsl:template match="indexterm" mode="index-div-basic">
-  <xsl:param name="scope" select="."/>
-  <xsl:param name="role" select="''"/>
-  <xsl:param name="type" select="''"/>
-
-  <xsl:variable name="key"
-                select="translate(substring(&primary;, 1, 1),
-                         &lowercase;,&uppercase;)"/>
-
-  <xsl:if test="key('letter', $key)[&scope;]
-                [count(.|key('primary', &primary;)[&scope;][1]) = 1]">
-    <div class="indexdiv">
-      <!-- pgsql-docs: added id attribute here for linking to it -->
-      <xsl:attribute name="id">
-        <xsl:value-of select="concat('indexdiv-', $key)"/>
-      </xsl:attribute>
-
-      <xsl:if test="contains(concat(&lowercase;, &uppercase;), $key)">
-        <h3>
-          <xsl:value-of select="translate($key, &lowercase;, &uppercase;)"/>
-        </h3>
-      </xsl:if>
-      <dl>
-        <xsl:apply-templates select="key('letter', $key)[&scope;]
-                                     [count(.|key('primary', &primary;)
-                                     [&scope;][1])=1]"
-                             mode="index-primary">
-          <xsl:with-param name="position" select="position()"/>
-          <xsl:with-param name="scope" select="$scope"/>
-          <xsl:with-param name="role" select="$role"/>
-          <xsl:with-param name="type" select="$type"/>
-          <xsl:sort select="translate(&primary;, &lowercase;, &uppercase;)"/>
-        </xsl:apply-templates>
-      </dl>
-    </div>
-  </xsl:if>
-</xsl:template>
-
-<!-- pgsql-docs -->
-<xsl:template match="indexterm" mode="index-div-quicklinks">
-  <xsl:param name="scope" select="."/>
-  <xsl:param name="role" select="''"/>
-  <xsl:param name="type" select="''"/>
-
-  <xsl:variable name="key"
-                select="translate(substring(&primary;, 1, 1),
-                        &lowercase;,&uppercase;)"/>
-
-  <xsl:if test="key('letter', $key)[&scope;]
-                [count(.|key('primary', &primary;)[&scope;][1]) = 1]">
-    <xsl:if test="contains(concat(&lowercase;, &uppercase;), $key)">
-      |
-      <a>
-        <xsl:attribute name="href">
-          <xsl:value-of select="concat('#indexdiv-', $key)"/>
-        </xsl:attribute>
-        <xsl:value-of select="translate($key, &lowercase;, &uppercase;)"/>
-      </a>
-    </xsl:if>
-  </xsl:if>
-</xsl:template>
-
-
-<!-- upper case HTML anchors for backward compatibility -->
-
-<xsl:template name="object.id">
-  <xsl:param name="object" select="."/>
-  <xsl:choose>
-    <xsl:when test="$object/@id">
-      <xsl:value-of select="translate($object/@id, &lowercase;, &uppercase;)"/>
-    </xsl:when>
-    <xsl:when test="$object/@xml:id">
-      <xsl:value-of select="$object/@xml:id"/>
-    </xsl:when>
-    <xsl:when test="$generate.consistent.ids != 0">
-      <!-- Make $object the current node -->
-      <xsl:for-each select="$object">
-        <xsl:text>id-</xsl:text>
-        <xsl:number level="multiple" count="*"/>
-      </xsl:for-each>
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:value-of select="generate-id($object)"/>
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-</xsl:stylesheet>

doc/stylesheet-html-nochunk.xsl

@@ -1,23 +0,0 @@
-<?xml version='1.0'?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                version='1.0'
-                xmlns="http://www.w3.org/TR/xhtml1/transitional"
-                exclude-result-prefixes="#default">
-
-<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"/>
-<xsl:include href="stylesheet-common.xsl" />
-<xsl:include href="stylesheet-html-common.xsl" />
-<xsl:include href="stylesheet-speedup-xhtml.xsl" />
-
-<!-- embed SVG images into output file -->
-<xsl:template match="imagedata[@format='SVG']">
-  <xsl:variable name="filename">
-    <xsl:call-template name="mediaobject.filename">
-      <xsl:with-param name="object" select=".."/>
-    </xsl:call-template>
-  </xsl:variable>
-
-  <xsl:copy-of select="document($filename)"/>
-</xsl:template>
-
-</xsl:stylesheet>

doc/stylesheet-speedup-common.xsl

@@ -1,100 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                version='1.0'>
-
-<!-- Performance-optimized versions of some upstream templates from common/
-     directory -->
-
-<!-- from common/labels.xsl -->
-
-<xsl:template match="chapter" mode="label.markup">
-  <xsl:choose>
-    <xsl:when test="@label">
-      <xsl:value-of select="@label"/>
-    </xsl:when>
-    <xsl:when test="string($chapter.autolabel) != 0">
-      <xsl:if test="$component.label.includes.part.label != 0 and
-                      ancestor::part">
-        <xsl:variable name="part.label">
-          <xsl:apply-templates select="ancestor::part"
-                               mode="label.markup"/>
-        </xsl:variable>
-        <xsl:if test="$part.label != ''">
-          <xsl:value-of select="$part.label"/>
-          <xsl:apply-templates select="ancestor::part"
-                               mode="intralabel.punctuation">
-            <xsl:with-param name="object" select="."/>
-          </xsl:apply-templates>
-        </xsl:if>
-      </xsl:if>
-      <xsl:variable name="format">
-        <xsl:call-template name="autolabel.format">
-          <xsl:with-param name="format" select="$chapter.autolabel"/>
-        </xsl:call-template>
-      </xsl:variable>
-      <xsl:choose>
-        <xsl:when test="$label.from.part != 0 and ancestor::part">
-          <xsl:number from="part" count="chapter" format="{$format}" level="any"/>
-        </xsl:when>
-        <xsl:otherwise>
-          <!-- Optimization for pgsql-docs: When counting to get label for
-               this chapter, preceding chapters can only be our siblings or
-               children of a preceding part, so only count those instead of
-               scanning the entire node tree. -->
-          <!-- <xsl:number from="book" count="chapter" format="{$format}" level="any"/> -->
-          <xsl:number value="count(../preceding-sibling::part/chapter) + count(preceding-sibling::chapter) + 1" format="{$format}"/>
-        </xsl:otherwise>
-      </xsl:choose>
-    </xsl:when>
-  </xsl:choose>
-</xsl:template>
-
-<xsl:template match="appendix" mode="label.markup">
-  <xsl:choose>
-    <xsl:when test="@label">
-      <xsl:value-of select="@label"/>
-    </xsl:when>
-    <xsl:when test="string($appendix.autolabel) != 0">
-      <xsl:if test="$component.label.includes.part.label != 0 and
-                      ancestor::part">
-        <xsl:variable name="part.label">
-          <xsl:apply-templates select="ancestor::part"
-                               mode="label.markup"/>
-        </xsl:variable>
-        <xsl:if test="$part.label != ''">
-          <xsl:value-of select="$part.label"/>
-          <xsl:apply-templates select="ancestor::part"
-                               mode="intralabel.punctuation">
-            <xsl:with-param name="object" select="."/>
-          </xsl:apply-templates>
-        </xsl:if>
-      </xsl:if>
-      <xsl:variable name="format">
-        <xsl:call-template name="autolabel.format">
-          <xsl:with-param name="format" select="$appendix.autolabel"/>
-        </xsl:call-template>
-      </xsl:variable>
-      <xsl:choose>
-        <xsl:when test="$label.from.part != 0 and ancestor::part">
-          <xsl:number from="part" count="appendix" format="{$format}" level="any"/>
-        </xsl:when>
-        <xsl:otherwise>
-          <!-- Optimization for pgsql-docs: When counting to get label for
-               this appendix, preceding appendixes can only be our siblings or
-               children of a preceding part, so only count those instead of
-               scanning the entire node tree. -->
-          <!-- <xsl:number from="book|article" count="appendix" format="{$format}" level="any"/> -->
-          <xsl:number value="count(../preceding-sibling::part/appendix) + count(preceding-sibling::appendix) + 1" format="{$format}"/>
-        </xsl:otherwise>
-      </xsl:choose>
-    </xsl:when>
-  </xsl:choose>
-</xsl:template>
-
-<!-- from common/l10n.xsl -->
-
-<!-- Just hardcode the language for the whole document, to make it faster. -->
-
-<xsl:template name="l10n.language">en</xsl:template>
-
-</xsl:stylesheet>

doc/stylesheet-speedup-xhtml.xsl

@@ -1,345 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                xmlns="http://www.w3.org/1999/xhtml"
-                version='1.0'>
-
-<!-- Performance-optimized versions of some upstream templates from xhtml/
-     directory -->
-
-<!-- from xhtml/autoidx.xsl -->
-
-<xsl:template match="indexterm" mode="reference">
-  <xsl:param name="scope" select="."/>
-  <xsl:param name="role" select="''"/>
-  <xsl:param name="type" select="''"/>
-  <xsl:param name="position"/>
-  <xsl:param name="separator" select="''"/>
-
-  <xsl:variable name="term.separator">
-    <xsl:call-template name="index.separator">
-      <xsl:with-param name="key" select="'index.term.separator'"/>
-    </xsl:call-template>
-  </xsl:variable>
-
-  <xsl:variable name="number.separator">
-    <xsl:call-template name="index.separator">
-      <xsl:with-param name="key" select="'index.number.separator'"/>
-    </xsl:call-template>
-  </xsl:variable>
-
-  <xsl:variable name="range.separator">
-    <xsl:call-template name="index.separator">
-      <xsl:with-param name="key" select="'index.range.separator'"/>
-    </xsl:call-template>
-  </xsl:variable>
-
-  <xsl:choose>
-    <xsl:when test="$separator != ''">
-      <xsl:value-of select="$separator"/>
-    </xsl:when>
-    <xsl:when test="$position = 1">
-      <xsl:value-of select="$term.separator"/>
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:value-of select="$number.separator"/>
-    </xsl:otherwise>
-  </xsl:choose>
-
-  <xsl:choose>
-    <xsl:when test="@zone and string(@zone)">
-      <xsl:call-template name="reference">
-        <xsl:with-param name="zones" select="normalize-space(@zone)"/>
-        <xsl:with-param name="position" select="position()"/>
-        <xsl:with-param name="scope" select="$scope"/>
-        <xsl:with-param name="role" select="$role"/>
-        <xsl:with-param name="type" select="$type"/>
-      </xsl:call-template>
-    </xsl:when>
-    <xsl:otherwise>
-      <a>
-        <xsl:apply-templates select="." mode="class.attribute"/>
-        <xsl:variable name="title">
-          <xsl:choose>
-            <xsl:when test="$index.prefer.titleabbrev != 0">
-              <xsl:apply-templates select="(ancestor-or-self::set|ancestor-or-self::book|ancestor-or-self::part|ancestor-or-self::reference|ancestor-or-self::partintro|ancestor-or-self::chapter|ancestor-or-self::appendix|ancestor-or-self::preface|ancestor-or-self::article|ancestor-or-self::section|ancestor-or-self::sect1|ancestor-or-self::sect2|ancestor-or-self::sect3|ancestor-or-self::sect4|ancestor-or-self::sect5|ancestor-or-self::refentry|ancestor-or-self::refsect1|ancestor-or-self::refsect2|ancestor-or-self::refsect3|ancestor-or-self::simplesect|ancestor-or-self::bibliography|ancestor-or-self::glossary|ancestor-or-self::index|ancestor-or-self::webpage|ancestor-or-self::topic)[last()]" mode="titleabbrev.markup"/>
-            </xsl:when>
-            <xsl:otherwise>
-              <xsl:apply-templates select="(ancestor-or-self::set|ancestor-or-self::book|ancestor-or-self::part|ancestor-or-self::reference|ancestor-or-self::partintro|ancestor-or-self::chapter|ancestor-or-self::appendix|ancestor-or-self::preface|ancestor-or-self::article|ancestor-or-self::section|ancestor-or-self::sect1|ancestor-or-self::sect2|ancestor-or-self::sect3|ancestor-or-self::sect4|ancestor-or-self::sect5|ancestor-or-self::refentry|ancestor-or-self::refsect1|ancestor-or-self::refsect2|ancestor-or-self::refsect3|ancestor-or-self::simplesect|ancestor-or-self::bibliography|ancestor-or-self::glossary|ancestor-or-self::index|ancestor-or-self::webpage|ancestor-or-self::topic)[last()]" mode="title.markup"/>
-            </xsl:otherwise>
-          </xsl:choose>
-        </xsl:variable>
-
-        <xsl:attribute name="href">
-          <xsl:choose>
-            <xsl:when test="$index.links.to.section = 1">
-              <xsl:call-template name="href.target">
-                <xsl:with-param name="object" select="(ancestor-or-self::set|ancestor-or-self::book|ancestor-or-self::part|ancestor-or-self::reference|ancestor-or-self::partintro|ancestor-or-self::chapter|ancestor-or-self::appendix|ancestor-or-self::preface|ancestor-or-self::article|ancestor-or-self::section|ancestor-or-self::sect1|ancestor-or-self::sect2|ancestor-or-self::sect3|ancestor-or-self::sect4|ancestor-or-self::sect5|ancestor-or-self::refentry|ancestor-or-self::refsect1|ancestor-or-self::refsect2|ancestor-or-self::refsect3|ancestor-or-self::simplesect|ancestor-or-self::bibliography|ancestor-or-self::glossary|ancestor-or-self::index|ancestor-or-self::webpage|ancestor-or-self::topic)[last()]"/>
-                <!-- Optimization for pgsql-docs: We only have an index as a
-                     child of book, so look that up directly instead of
-                     scanning the entire node tree.  Also, don't look for
-                     setindex. -->
-                <!-- <xsl:with-param name="context" select="(//index[count(ancestor::node()|$scope) = count(ancestor::node()) and ($role = @role or $type = @type or (string-length($role) = 0 and string-length($type) = 0))] | //setindex[count(ancestor::node()|$scope) = count(ancestor::node()) and ($role = @role or $type = @type or (string-length($role) = 0 and string-length($type) = 0))])[1]"/> -->
-                <xsl:with-param name="context" select="(/book/index[count(ancestor::node()|$scope) = count(ancestor::node()) and ($role = @role or $type = @type or (string-length($role) = 0 and string-length($type) = 0))])[1]"/>
-              </xsl:call-template>
-            </xsl:when>
-            <xsl:otherwise>
-              <xsl:call-template name="href.target">
-                <xsl:with-param name="object" select="."/>
-                <xsl:with-param name="context" select="(//index[count(ancestor::node()|$scope) = count(ancestor::node()) and ($role = @role or $type = @type or (string-length($role) = 0 and string-length($type) = 0))] | //setindex[count(ancestor::node()|$scope) = count(ancestor::node()) and ($role = @role or $type = @type or (string-length($role) = 0 and string-length($type) = 0))])[1]"/>
-              </xsl:call-template>
-            </xsl:otherwise>
-          </xsl:choose>
-
-        </xsl:attribute>
-
-        <xsl:value-of select="$title"/> <!-- text only -->
-      </a>
-
-      <xsl:variable name="id" select="(@id|@xml:id)[1]"/>
-      <xsl:if test="key('endofrange', $id)[count(ancestor::node()|$scope) = count(ancestor::node()) and ($role = @role or $type = @type or (string-length($role) = 0 and string-length($type) = 0))]">
-        <xsl:apply-templates select="key('endofrange', $id)[count(ancestor::node()|$scope) = count(ancestor::node()) and ($role = @role or $type = @type or (string-length($role) = 0 and string-length($type) = 0))][last()]" mode="reference">
-          <xsl:with-param name="position" select="position()"/>
-          <xsl:with-param name="scope" select="$scope"/>
-          <xsl:with-param name="role" select="$role"/>
-          <xsl:with-param name="type" select="$type"/>
-          <xsl:with-param name="separator" select="$range.separator"/>
-        </xsl:apply-templates>
-      </xsl:if>
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-<xsl:template name="reference">
-  <xsl:param name="scope" select="."/>
-  <xsl:param name="role" select="''"/>
-  <xsl:param name="type" select="''"/>
-  <xsl:param name="zones"/>
-
-  <xsl:choose>
-    <xsl:when test="contains($zones, ' ')">
-      <xsl:variable name="zone" select="substring-before($zones, ' ')"/>
-      <xsl:variable name="target" select="key('sections', $zone)"/>
-
-      <a>
-        <xsl:apply-templates select="." mode="class.attribute"/>
-<!--    Optimization for pgsql-docs: this call adds nothing but fails with docbook-xsl 1.76 -->
-<!--    <xsl:call-template name="id.attribute"/> -->
-        <xsl:attribute name="href">
-          <xsl:call-template name="href.target">
-            <xsl:with-param name="object" select="$target[1]"/>
-            <xsl:with-param name="context" select="//index[count(ancestor::node()|$scope) = count(ancestor::node()) and ($role = @role or $type = @type or (string-length($role) = 0 and string-length($type) = 0))][1]"/>
-          </xsl:call-template>
-        </xsl:attribute>
-        <xsl:apply-templates select="$target[1]" mode="index-title-content"/>
-      </a>
-      <xsl:text>, </xsl:text>
-      <xsl:call-template name="reference">
-        <xsl:with-param name="zones" select="substring-after($zones, ' ')"/>
-        <xsl:with-param name="position" select="position()"/>
-        <xsl:with-param name="scope" select="$scope"/>
-        <xsl:with-param name="role" select="$role"/>
-        <xsl:with-param name="type" select="$type"/>
-      </xsl:call-template>
-    </xsl:when>
-    <xsl:otherwise>
-      <xsl:variable name="zone" select="$zones"/>
-      <xsl:variable name="target" select="key('sections', $zone)"/>
-
-      <a>
-        <xsl:apply-templates select="." mode="class.attribute"/>
-<!--    Optimization for pgsql-docs: this call adds nothing but fails with docbook-xsl 1.76 -->
-<!--    <xsl:call-template name="id.attribute"/> -->
-        <xsl:attribute name="href">
-          <xsl:call-template name="href.target">
-            <xsl:with-param name="object" select="$target[1]"/>
-            <!-- Optimization for pgsql-docs: Only look for index under book
-                 instead of searching the whole node tree. -->
-            <!-- <xsl:with-param name="context" select="//index[count(ancestor::node()|$scope) = count(ancestor::node()) and ($role = @role or $type = @type or (string-length($role) = 0 and string-length($type) = 0))][1]"/> -->
-            <xsl:with-param name="context" select="/book/index[count(ancestor::node()|$scope) = count(ancestor::node()) and ($role = @role or $type = @type or (string-length($role) = 0 and string-length($type) = 0))][1]"/>
-          </xsl:call-template>
-        </xsl:attribute>
-        <xsl:apply-templates select="$target[1]" mode="index-title-content"/>
-      </a>
-    </xsl:otherwise>
-  </xsl:choose>
-</xsl:template>
-
-
-<!-- from xhtml/chunk-common.xsl -->
-
-<xsl:template name="chunk-all-sections">
-  <xsl:param name="content">
-    <xsl:apply-imports/>
-  </xsl:param>
-
-  <!-- Optimization for pgsql-docs: Since we set a fixed $chunk.section.depth,
-       we can do away with a bunch of complicated XPath searches for the
-       previous and next sections at various levels. -->
-
-  <xsl:if test="$chunk.section.depth != 1">
-    <xsl:message terminate="yes">
-      <xsl:text>Error: If you change $chunk.section.depth, then you must update the performance-optimized chunk-all-sections-template.</xsl:text>
-    </xsl:message>
-  </xsl:if>
-
-  <xsl:variable name="prev"
-    select="(preceding::book[1]
-             |preceding::preface[1]
-             |preceding::chapter[1]
-             |preceding::appendix[1]
-             |preceding::part[1]
-             |preceding::reference[1]
-             |preceding::refentry[1]
-             |preceding::colophon[1]
-             |preceding::article[1]
-             |preceding::topic[1]
-             |preceding::bibliography[parent::article or parent::book or parent::part][1]
-             |preceding::glossary[parent::article or parent::book or parent::part][1]
-             |preceding::index[$generate.index != 0]
-                               [parent::article or parent::book or parent::part][1]
-             |preceding::setindex[$generate.index != 0][1]
-             |ancestor::set
-             |ancestor::book[1]
-             |ancestor::preface[1]
-             |ancestor::chapter[1]
-             |ancestor::appendix[1]
-             |ancestor::part[1]
-             |ancestor::reference[1]
-             |ancestor::article[1]
-             |ancestor::topic[1]
-             |preceding::sect1[1]
-             |ancestor::sect1[1])[last()]"/>
-
-  <xsl:variable name="next"
-    select="(following::book[1]
-             |following::preface[1]
-             |following::chapter[1]
-             |following::appendix[1]
-             |following::part[1]
-             |following::reference[1]
-             |following::refentry[1]
-             |following::colophon[1]
-             |following::bibliography[parent::article or parent::book or parent::part][1]
-             |following::glossary[parent::article or parent::book or parent::part][1]
-             |following::index[$generate.index != 0]
-                               [parent::article or parent::book][1]
-             |following::article[1]
-             |following::topic[1]
-             |following::setindex[$generate.index != 0][1]
-             |descendant::book[1]
-             |descendant::preface[1]
-             |descendant::chapter[1]
-             |descendant::appendix[1]
-             |descendant::article[1]
-             |descendant::topic[1]
-             |descendant::bibliography[parent::article or parent::book][1]
-             |descendant::glossary[parent::article or parent::book or parent::part][1]
-             |descendant::index[$generate.index != 0]
-                                [parent::article or parent::book][1]
-             |descendant::colophon[1]
-             |descendant::setindex[$generate.index != 0][1]
-             |descendant::part[1]
-             |descendant::reference[1]
-             |descendant::refentry[1]
-             |following::sect1[1]
-             |descendant::sect1[1])[1]"/>
-
-  <xsl:call-template name="process-chunk">
-    <xsl:with-param name="prev" select="$prev"/>
-    <xsl:with-param name="next" select="$next"/>
-    <xsl:with-param name="content" select="$content"/>
-  </xsl:call-template>
-</xsl:template>
-
-<xsl:template name="href.target">
-  <xsl:param name="context" select="."/>
-  <xsl:param name="object" select="."/>
-  <xsl:param name="toc-context" select="."/>
-  <!-- Optimization for pgsql-docs: Remove support for dbhtml processing
-       instruction here -->
-  <xsl:variable name="href.to.uri">
-    <xsl:call-template name="href.target.uri">
-      <xsl:with-param name="object" select="$object"/>
-    </xsl:call-template>
-  </xsl:variable>
-  <xsl:variable name="href.from.uri">
-    <xsl:choose>
-      <xsl:when test="not($toc-context = .)">
-        <xsl:call-template name="href.target.uri">
-          <xsl:with-param name="object" select="$toc-context"/>
-        </xsl:call-template>
-      </xsl:when>
-      <xsl:otherwise>
-        <xsl:call-template name="href.target.uri">
-          <xsl:with-param name="object" select="$context"/>
-        </xsl:call-template>
-      </xsl:otherwise>
-    </xsl:choose>
-  </xsl:variable>
-  <xsl:variable name="href.to">
-    <xsl:value-of select="$href.to.uri"/>
-  </xsl:variable>
-  <xsl:variable name="href.from">
-    <xsl:call-template name="trim.common.uri.paths">
-      <xsl:with-param name="uriA" select="$href.to.uri"/>
-      <xsl:with-param name="uriB" select="$href.from.uri"/>
-      <xsl:with-param name="return" select="'B'"/>
-    </xsl:call-template>
-  </xsl:variable>
-  <xsl:variable name="depth">
-    <xsl:call-template name="count.uri.path.depth">
-      <xsl:with-param name="filename" select="$href.from"/>
-    </xsl:call-template>
-  </xsl:variable>
-  <xsl:variable name="href">
-    <xsl:call-template name="copy-string">
-      <xsl:with-param name="string" select="'../'"/>
-      <xsl:with-param name="count" select="$depth"/>
-    </xsl:call-template>
-    <xsl:value-of select="$href.to"/>
-  </xsl:variable>
-  <xsl:value-of select="$href"/>
-</xsl:template>
-
-<xsl:template name="html.head">
-  <xsl:param name="prev" select="/foo"/>
-  <xsl:param name="next" select="/foo"/>
-
-  <!-- Optimization for pgsql-docs: Cut out a bunch of things we don't need
-       here, including an expensive //legalnotice search. -->
-
-  <head>
-    <xsl:call-template name="system.head.content"/>
-    <xsl:call-template name="head.content"/>
-
-    <xsl:if test="$prev">
-      <link rel="prev">
-        <xsl:attribute name="href">
-          <xsl:call-template name="href.target">
-            <xsl:with-param name="object" select="$prev"/>
-          </xsl:call-template>
-        </xsl:attribute>
-        <xsl:attribute name="title">
-          <xsl:apply-templates select="$prev" mode="object.title.markup.textonly"/>
-        </xsl:attribute>
-      </link>
-    </xsl:if>
-
-    <xsl:if test="$next">
-      <link rel="next">
-        <xsl:attribute name="href">
-          <xsl:call-template name="href.target">
-            <xsl:with-param name="object" select="$next"/>
-          </xsl:call-template>
-        </xsl:attribute>
-        <xsl:attribute name="title">
-          <xsl:apply-templates select="$next" mode="object.title.markup.textonly"/>
-        </xsl:attribute>
-      </link>
-    </xsl:if>
-
-    <xsl:call-template name="user.head.content"/>
-  </head>
-</xsl:template>
-
-</xsl:stylesheet>

doc/stylesheet.css

@@ -1,471 +0,0 @@
-/* PostgreSQL.org Documentation Style */
-
-@import 'website-docs.css';
-
-/* requires global.css, table.css and text.css to be loaded before this file! */
-body {
-  font-family: verdana, sans-serif;
-  font-size: 76%;
-  background: url("/resources/background.png") repeat-x scroll left top transparent;
-  padding: 15px 4%;
-  margin: 0;
-}
-
-/* monospace font size fix */
-pre, code, kbd, samp, tt {
-  font-family: monospace,monospace;
-  font-size: 1em;
-}
-
-div.NAVHEADER table {
-  margin-left: 0;
-}
-
-/* Container Definitions */
-
-#docContainerWrap {
-  text-align: center; /* Win IE5 */
-}
-
-#docContainer {
-  margin: 0 auto;
-  width: 90%;
-  padding-bottom: 2em;
-  display: block;
-  text-align: left; /* Win IE5 */
-}
-
-#docHeader {
-  background-image: url("/media/img/docs/bg_hdr.png");
-  height: 83px;
-  margin: 0px;
-  padding: 0px;
-  display: block;
-}
-
-#docHeaderLogo {
-  position: relative;
-  width: 206px;
-  height: 83px;
-  border: 0px;
-  padding: 0px;
-  margin: 0 0 0 20px;
-}
-
-#docHeaderLogo img {
-  border: 0px;
-}
-
-#docNavSearchContainer {
-  padding-bottom: 2px;
-}
-
-#docNav, #docVersions {
-  position: relative;
-  text-align: left;
-  margin-left: 10px;
-  margin-top: 5px;
-  color: #666;
-  font-size: 0.95em;
-}
-
-#docSearch {
-  position: relative;
-  text-align: right;
-  padding: 0;
-  margin: 0;
-  color: #666;
-}
-
-#docTextSize {
-  text-align: right;
-  white-space: nowrap;
-  margin-top: 7px;
-  font-size: 0.95em;
-}
-
-#docSearch form {
-  position: relative;
-  top: 5px;
-  right: 0;
-  margin: 0; /* need for IE 5.5 OSX */
-  text-align: right; /* need for IE 5.5 OSX */
-  white-space: nowrap; /* for Opera */
-}
-
-#docSearch form label {
-  color: #666;
-  font-size: 0.95em;
-}
-
-#docSearch form input {
-  font-size: 0.95em;
-}
-  
-#docSearch form #submit {
-  font-size: 0.95em;
-  background: #7A7A7A;
-  color: #fff;
-  border: 1px solid #7A7A7A;
-  padding: 1px 4px;
-}
-  
-#docSearch form #q {
-  width: 170px;
-  font-size: 0.95em;
-  border:  1px solid #7A7A7A;
-  background: #E1E1E1;
-  color: #000000;
-  padding: 2px;
-}
-
-.frmDocSearch {
-  padding: 0;
-  margin: 0;
-  display: inline;
-}
-
-.inpDocSearch {
-  padding: 0;
-  margin: 0;
-  color: #000;
-}
-
-#docContent {
-  position: relative;
-  margin-left: 10px;
-  margin-right: 10px;
-  margin-top: 40px;
-}
-
-#docFooter {
-  position: relative;
-  font-size: 0.9em; 
-  color: #666; 
-  line-height: 1.3em; 
-  margin-left: 10px;
-  margin-right: 10px;
-}
-
-#docComments {
-  margin-top: 10px;
-}
-
-#docClear {
-  clear: both;
-  margin: 0;
-  padding: 0;
-}
-
-/* Heading Definitions */
-
-h1, h2, h3 {
-  font-weight: bold;
-  margin-top: 2ex;
-  color: #444;
-}
-
-h1 {
-  font-size: 1.4em;
-}
-
-h2 {
-  font-size: 1.2em !important;
-}
-
-h3 {
-  font-size: 1.1em;
-}
-
-h1 a:hover,
-h2 a:hover,
-h3 a:hover,
-h4 a:hover {
-  color: #444;
-  text-decoration: none;
-}
-
-/* Text Styles */
-
-div.SECT2 {
-  margin-top: 4ex;
-}
-
-div.SECT3 {
-  margin-top: 3ex;
-  margin-left: 3ex;
-}
-
-.txtCurrentLocation {
-  font-weight: bold;
-}
-
-p, ol, ul, li {
-  line-height: 1.5em;
-}
-
-.txtCommentsWrap {
-  border: 2px solid #F5F5F5; 
-  width: 100%;
-}
-
-.txtCommentsContent {
-  background: #F5F5F5;
-  padding: 3px;
-}
-
-.txtCommentsPoster {
-  float: left;
-}
-
-.txtCommentsDate {
-  float: right;
-}
-
-.txtCommentsComment {
-  padding: 3px;
-}
-
-#docContainer pre code,
-#docContainer pre tt,
-#docContainer pre pre,
-#docContainer tt tt,
-#docContainer tt code,
-#docContainer tt pre {
-  font-size: 1em;
-}
-
-pre.LITERALLAYOUT,
-.SCREEN,
-.SYNOPSIS,
-.PROGRAMLISTING,
-.REFSYNOPSISDIV p,
-table.CAUTION,
-table.WARNING,
-blockquote.NOTE,
-blockquote.TIP,
-table.CALSTABLE {
-  -moz-box-shadow: 3px 3px 5px #DFDFDF;
-  -webkit-box-shadow: 3px 3px 5px #DFDFDF;
-  -khtml-box-shadow: 3px 3px 5px #DFDFDF;
-  -o-box-shadow: 3px 3px 5px #DFDFDF;
-  box-shadow: 3px 3px 5px #DFDFDF;
-}
-
-pre.LITERALLAYOUT,
-.SCREEN,
-.SYNOPSIS,
-.PROGRAMLISTING,
-.REFSYNOPSISDIV p,
-table.CAUTION,
-table.WARNING,
-blockquote.NOTE,
-blockquote.TIP {
-  color: black;
-  border-width: 1px;
-  border-style: solid;
-  padding: 2ex;
-  margin: 2ex 0 2ex 2ex;
-  overflow: auto;
-  -moz-border-radius: 8px;
-  -webkit-border-radius: 8px;
-  -khtml-border-radius: 8px;
-  border-radius: 8px;
-}
-
-pre.LITERALLAYOUT,
-pre.SYNOPSIS,
-pre.PROGRAMLISTING,
-.REFSYNOPSISDIV p,
-.SCREEN {
-  border-color: #CFCFCF;
-  background-color: #F7F7F7;
-}
-
-blockquote.NOTE,
-blockquote.TIP {
-  border-color: #DBDBCC;
-  background-color: #EEEEDD;
-  padding: 14px;
-  width: 572px;
-}
-
-blockquote.NOTE,
-blockquote.TIP,
-table.CAUTION,
-table.WARNING {
-  margin: 4ex auto;
-}
-
-blockquote.NOTE p,
-blockquote.TIP p {
-  margin: 0;
-}
-
-blockquote.NOTE pre,
-blockquote.NOTE code,
-blockquote.TIP pre,
-blockquote.TIP code {
-  margin-left: 0;
-  margin-right: 0;
-  -moz-box-shadow: none;
-  -webkit-box-shadow: none;
-  -khtml-box-shadow: none;
-  -o-box-shadow: none;
-  box-shadow: none;
-}
-
-.emphasis,
-.c2 {
-  font-weight: bold;
-}
-
-.REPLACEABLE {
-  font-style: italic;
-}
-
-/* Table Styles */
-
-table {
-  margin-left: 2ex;
-}
-
-table.CALSTABLE td,
-table.CALSTABLE th,
-table.CAUTION td,
-table.CAUTION th,
-table.WARNING td,
-table.WARNING th {
-  border-style: solid;
-}
-
-table.CALSTABLE,
-table.CAUTION,
-table.WARNING {
-  border-spacing: 0;
-  border-collapse: collapse;
-}
-
-table.CALSTABLE
-{
-  margin: 2ex 0 2ex 2ex;
-  background-color: #E0ECEF;
-  border: 2px solid #A7C6DF;
-}
-
-table.CALSTABLE tr:hover td
-{
-  background-color: #EFEFEF;
-}
-
-table.CALSTABLE td {
-  background-color: #FFF;
-}
-
-table.CALSTABLE td,
-table.CALSTABLE th {
-  border: 1px solid #A7C6DF;
-  padding: 0.5ex 0.5ex;
-}
-
-table.CAUTION,
-table.WARNING {
-  border-collapse: separate;
-  display: block;
-  padding: 0;
-  max-width: 600px;
-}
-
-table.CAUTION {
-  background-color: #F5F5DC;
-  border-color: #DEDFA7;
-}
-
-table.WARNING {
-  background-color: #FFD7D7;
-  border-color: #DF421E;
-}
-
-table.CAUTION td,
-table.CAUTION th,
-table.WARNING td,
-table.WARNING th {
-  border-width: 0;
-  padding-left: 2ex;
-  padding-right: 2ex;
-}
-
-table.CAUTION td,
-table.CAUTION th {
-  border-color: #F3E4D5
-}
-
-table.WARNING td,
-table.WARNING th {
-  border-color: #FFD7D7;
-}
-
-td.c1,
-td.c2,
-td.c3,
-td.c4,
-td.c5,
-td.c6 {
-  font-size: 1.1em;
-  font-weight: bold;
-  border-bottom: 0px solid #FFEFEF;
-  padding: 1ex 2ex 0;
-}
-
-/* Link Styles */
-
-#docNav a {
-  font-weight: bold;
-}
-
-a:link,
-a:visited,
-a:active,
-a:hover {
-  text-decoration: underline;
-}
-
-a:link,
-a:active {
-  color:#0066A2;
-}
-
-a:visited {
-  color:#004E66;
-}
-
-a:hover {
-  color:#000000;
-}
-
-#docFooter a:link,
-#docFooter a:visited,
-#docFooter a:active {
-  color:#666;
-}
-
-#docContainer code.FUNCTION tt {
-  font-size: 1em;
-}
-
-div.header {
-    color: #444;
-    margin-top: 5px;
-}
-
-div.footer {
-    text-align: center;
-    background-image: url("/resources/footerl.png"), url("/resources/footerr.png"), url("/resources/footerc.png");
-    background-position: left top, right top, center top;
-    background-repeat: no-repeat, no-repeat, repeat-x;
-    padding-top: 45px;
-}
-
-img {
-    border-style: none;
-}

doc/stylesheet.dsl

@@ -1,851 +0,0 @@
-<!-- doc/src/sgml/stylesheet.dsl -->
-<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [
-
-<!-- must turn on one of these with -i on the jade command line -->
-<!ENTITY % output-html          "IGNORE">
-<!ENTITY % output-print         "IGNORE">
-<!ENTITY % output-text          "IGNORE">
-
-<![ %output-html; [
-<!ENTITY dbstyle PUBLIC "-//Norman Walsh//DOCUMENT DocBook HTML Stylesheet//EN" CDATA DSSSL>
-]]>
-
-<![ %output-print; [
-<!ENTITY dbstyle PUBLIC "-//Norman Walsh//DOCUMENT DocBook Print Stylesheet//EN" CDATA DSSSL>
-]]>
-
-<![ %output-text; [
-<!ENTITY dbstyle PUBLIC "-//Norman Walsh//DOCUMENT DocBook HTML Stylesheet//EN" CDATA DSSSL>
-]]>
-
-]>
-
-<style-sheet>
- <style-specification use="docbook">
-  <style-specification-body>
-
-<!-- general customization ......................................... -->
-
-<!-- (applicable to all output formats) -->
-
-(define draft-mode              #f)
-
-;; Don't show manpage volume numbers
-(define %refentry-xref-manvolnum% #f)
-
-;; Don't use graphics for callouts.  (We could probably do that, but
-;; it needs extra work.)
-(define %callout-graphics%      #f)
-
-;; Show comments during the development stage.
-(define %show-comments%         draft-mode)
-
-;; Force a chapter TOC even if it includes only a single entry
-(define %force-chapter-toc% #t)
-
-;; Don't append period if run-in title ends with any of these
-;; characters.  We had to add the colon here.  This is fixed in
-;; stylesheets version 1.71, so it can be removed sometime.
-(define %content-title-end-punct%
-  '(#\. #\! #\? #\:))
-
-;; No automatic punctuation after honorific name parts
-(define %honorific-punctuation% "")
-
-;; Change display of some elements
-(element command ($mono-seq$))
-(element envar ($mono-seq$))
-(element lineannotation ($italic-seq$))
-(element literal ($mono-seq$))
-(element option ($mono-seq$))
-(element parameter ($mono-seq$))
-(element structfield ($mono-seq$))
-(element structname ($mono-seq$))
-(element symbol ($mono-seq$))
-(element token ($mono-seq$))
-(element type ($mono-seq$))
-(element varname ($mono-seq$))
-(element (programlisting emphasis) ($bold-seq$)) ;; to highlight sections of code
-
-;; Special support for Tcl synopses
-(element optional
-  (if (equal? (attribute-string (normalize "role")) "tcl")
-      (make sequence
-        (literal "?")
-        ($charseq$)
-        (literal "?"))
-      (make sequence
-        (literal %arg-choice-opt-open-str%)
-        ($charseq$)
-        (literal %arg-choice-opt-close-str%))))
-
-;; Avoid excessive cross-reference labels
-(define (auto-xref-indirect? target ancestor)
-  (cond
-;   ;; Always add indirect references to another book
-;   ((member (gi ancestor) (book-element-list))
-;    #t)
-   ;; Add indirect references to the section or component a block
-   ;; is in iff chapters aren't autolabelled.  (Otherwise "Figure 1-3"
-   ;; is sufficient)
-   ((and (member (gi target) (block-element-list))
-         (not %chapter-autolabel%))
-    #t)
-   ;; Add indirect references to the component a section is in if
-   ;; the sections are not autolabelled
-   ((and (member (gi target) (section-element-list))
-         (member (gi ancestor) (component-element-list))
-         (not %section-autolabel%))
-    #t)
-   (else #f)))
-
-
-;; Bibliography things
-
-;; Use the titles of bibliography entries in cross-references
-(define biblio-xref-title       #t)
-
-;; Process bibliography entry components in the order shown below, not
-;; in the order they appear in the document.  (I suppose this should
-;; be made to fit some publishing standard.)
-(define %biblioentry-in-entry-order% #f)
-
-(define (biblioentry-inline-elements)
-  (list
-   (normalize "author")
-   (normalize "authorgroup")
-   (normalize "title")
-   (normalize "subtitle")
-   (normalize "volumenum")
-   (normalize "edition")
-   (normalize "othercredit")
-   (normalize "contrib")
-   (normalize "editor")
-   (normalize "publishername")
-   (normalize "confgroup")
-   (normalize "publisher")
-   (normalize "isbn")
-   (normalize "issn")
-   (normalize "pubsnumber")
-   (normalize "date")
-   (normalize "pubdate")
-   (normalize "pagenums")
-   (normalize "bibliomisc")))
-
-(mode biblioentry-inline-mode
-
-  (element confgroup
-    (make sequence
-      (literal "Proc. ")
-      (next-match)))
-
-  (element isbn
-    (make sequence
-      (literal "ISBN ")
-      (process-children)))
-
-  (element issn
-    (make sequence
-      (literal "ISSN ")
-      (process-children))))
-
-
-;; The rules in the default stylesheet for productname format it as a
-;; paragraph.  This may be suitable for productname directly within
-;; *info, but it's nonsense when productname is used inline, as we do.
-(mode book-titlepage-recto-mode
-  (element (para productname) ($charseq$)))
-(mode book-titlepage-verso-mode
-  (element (para productname) ($charseq$)))
-;; Add more here if needed...
-
-
-;; Replace a sequence of whitespace in a string by a single space
-(define (normalize-whitespace str #!optional (whitespace '(#\space #\U-000D)))
-  (let loop ((characters (string->list str))
-             (result '())
-             (prev-was-space #f))
-    (if (null? characters)
-        (list->string (reverse result))
-        (let ((c (car characters))
-              (rest (cdr characters)))
-          (if (member c whitespace)
-              (if prev-was-space
-                  (loop rest result #t)
-                  (loop rest (cons #\space result) #t))
-              (loop rest (cons c result) #f))))))
-
-
-<!-- HTML output customization ..................................... -->
-
-<![ %output-html; [
-
-(define %section-autolabel%     #t)
-(define %label-preface-sections% #f)
-(define %generate-legalnotice-link% #t)
-(define %html-ext%              ".html")
-(define %root-filename%         "index")
-(define %link-mailto-url%       (string-append "mailto: repmgr-list@2ndquadrant.com"))
-(define %use-id-as-filename%    #t)
-(define website-build           #f)
-(define %stylesheet%            (if website-build "/resources/docs.css" "website-docs.css"))
-(define %graphic-default-extension% "gif")
-(define %body-attr%             '())
-(define ($generate-book-lot-list$) '())
-(define use-output-dir          #t)
-(define %output-dir%            "html")
-(define html-index-filename     "../HTML.index")
-
-
-;; Only build HTML.index or the actual HTML output, not both.  Saves a
-;; *lot* of time.  (overrides docbook.dsl)
-(root
-   (if (not html-index)
-       (make sequence
-         (process-children)
-         (with-mode manifest
-           (process-children)))
-       (with-mode htmlindex
-         (process-children))))
-
-
-;; Do not combine first section into chapter chunk.
-(define (chunk-skip-first-element-list) '())
-
-;; Returns the depth of auto TOC that should be made at the nd-level
-(define (toc-depth nd)
-  (cond ((string=? (gi nd) (normalize "book")) 2)
-        ((string=? (gi nd) (normalize "part")) 2)
-        ((string=? (gi nd) (normalize "chapter")) 2)
-        (else 1)))
-
-;; Add character encoding and time of creation into HTML header
-(define %html-header-tags%
-  (list (list "META" '("HTTP-EQUIV" "Content-Type") '("CONTENT" "text/html; charset=ISO-8859-1"))
-        (list "META" '("NAME" "creation") (list "CONTENT" (time->string (time) #t)))))
-
-
-;; Block elements are allowed in PARA in DocBook, but not in P in
-;; HTML.  With %fix-para-wrappers% turned on, the stylesheets attempt
-;; to avoid putting block elements in HTML P tags by outputting
-;; additional end/begin P pairs around them.
-(define %fix-para-wrappers% #t)
-
-;; ...but we need to do some extra work to make the above apply to PRE
-;; as well.  (mostly pasted from dbverb.dsl)
-(define ($verbatim-display$ indent line-numbers?)
-  (let ((content (make element gi: "PRE"
-                       attributes: (list
-                                    (list "CLASS" (gi)))
-                       (if (or indent line-numbers?)
-                           ($verbatim-line-by-line$ indent line-numbers?)
-                           (process-children)))))
-    (if %shade-verbatim%
-        (make element gi: "TABLE"
-              attributes: ($shade-verbatim-attr$)
-              (make element gi: "TR"
-                    (make element gi: "TD"
-                          content)))
-        (make sequence
-          (para-check)
-          content
-          (para-check 'restart)))))
-
-;; ...and for notes.
-(element note
-  (make sequence
-    (para-check)
-    ($admonition$)
-    (para-check 'restart)))
-
-;;; XXX The above is very ugly.  It might be better to run 'tidy' on
-;;; the resulting *.html files.
-
-
-;; Format multiple terms in varlistentry vertically, instead
-;; of comma-separated.
-(element (varlistentry term)
-  (make sequence
-    (process-children-trim)
-    (if (not (last-sibling?))
-        (make empty-element gi: "BR")
-        (empty-sosofo))))
-
-
-;; Customization of header
-;; - make title a link to the home page
-;; - add tool tips to Prev/Next links
-;; - add Up link
-;; (overrides dbnavig.dsl)
-(define (default-header-nav-tbl-noff elemnode prev next prevsib nextsib)
-  (let* ((r1? (nav-banner? elemnode))
-         (r1-sosofo (make element gi: "TR"
-                          (make element gi: "TH"
-                                attributes: (list
-                                             (list "COLSPAN" "4")
-                                             (list "ALIGN" "center")
-                                             (list "VALIGN" "bottom"))
-                                (make element gi: "A"
-                                      attributes: (list
-                                                   (list "HREF" (href-to (nav-home elemnode))))
-                                      (nav-banner elemnode)))))
-         (r2? (or (not (node-list-empty? prev))
-                  (not (node-list-empty? next))
-                  (nav-context? elemnode)))
-         (r2-sosofo (make element gi: "TR"
-                          (make element gi: "TD"
-                                attributes: (list
-                                             (list "WIDTH" "10%")
-                                             (list "ALIGN" "left")
-                                             (list "VALIGN" "top"))
-                                (if (node-list-empty? prev)
-                                    (make entity-ref name: "nbsp")
-                                    (make element gi: "A"
-                                          attributes: (list
-                                                       (list "TITLE" (element-title-string prev))
-                                                       (list "HREF"
-                                                             (href-to
-                                                              prev))
-                                                       (list "ACCESSKEY"
-                                                             "P"))
-                                          (gentext-nav-prev prev))))
-                          (make element gi: "TD"
-                                attributes: (list
-                                             (list "WIDTH" "10%")
-                                             (list "ALIGN" "left")
-                                             (list "VALIGN" "top"))
-                                (if (nav-up? elemnode)
-                                    (nav-up elemnode)
-                                    (nav-home-link elemnode)))
-                          (make element gi: "TD"
-                                attributes: (list
-                                             (list "WIDTH" "60%")
-                                             (list "ALIGN" "center")
-                                             (list "VALIGN" "bottom"))
-                                (nav-context elemnode))
-                          (make element gi: "TD"
-                                attributes: (list
-                                             (list "WIDTH" "20%")
-                                             (list "ALIGN" "right")
-                                             (list "VALIGN" "top"))
-                                (if (node-list-empty? next)
-                                    (make entity-ref name: "nbsp")
-                                    (make element gi: "A"
-                                          attributes: (list
-                                                       (list "TITLE" (element-title-string next))
-                                                       (list "HREF"
-                                                             (href-to
-                                                              next))
-                                                       (list "ACCESSKEY"
-                                                             "N"))
-                                          (gentext-nav-next next)))))))
-    (if (or r1? r2?)
-        (make element gi: "DIV"
-              attributes: '(("CLASS" "NAVHEADER"))
-          (make element gi: "TABLE"
-                attributes: (list
-                             (list "SUMMARY" "Header navigation table")
-                             (list "WIDTH" %gentext-nav-tblwidth%)
-                             (list "BORDER" "0")
-                             (list "CELLPADDING" "0")
-                             (list "CELLSPACING" "0"))
-                (if r1? r1-sosofo (empty-sosofo))
-                (if r2? r2-sosofo (empty-sosofo)))
-          (make empty-element gi: "HR"
-                attributes: (list
-                             (list "ALIGN" "LEFT")
-                             (list "WIDTH" %gentext-nav-tblwidth%))))
-        (empty-sosofo))))
-
-
-;; Put index "quicklinks" (A | B | C | ...) at the top of the bookindex page.
-
-(element index
-  (let ((preamble (node-list-filter-by-not-gi
-                   (children (current-node))
-                   (list (normalize "indexentry"))))
-        (indexdivs  (node-list-filter-by-gi
-                     (children (current-node))
-                     (list (normalize "indexdiv"))))
-        (entries  (node-list-filter-by-gi
-                   (children (current-node))
-                   (list (normalize "indexentry")))))
-    (html-document
-     (with-mode head-title-mode
-       (literal (element-title-string (current-node))))
-     (make element gi: "DIV"
-           attributes: (list (list "CLASS" (gi)))
-           ($component-separator$)
-           ($component-title$)
-           (if (node-list-empty? indexdivs)
-               (empty-sosofo)
-               (make element gi: "P"
-                     attributes: (list (list "CLASS" "INDEXDIV-QUICKLINKS"))
-                     (with-mode indexdiv-quicklinks-mode
-                       (process-node-list indexdivs))))
-           (process-node-list preamble)
-           (if (node-list-empty? entries)
-               (empty-sosofo)
-               (make element gi: "DL"
-                     (process-node-list entries)))))))
-
-
-(mode indexdiv-quicklinks-mode
-  (element indexdiv
-    (make sequence
-      (make element gi: "A"
-            attributes: (list (list "HREF" (href-to (current-node))))
-            (element-title-sosofo))
-      (if (not (last-sibling?))
-          (literal " | ")
-          (literal "")))))
-
-
-;; Changed to strip and normalize index term content (overrides
-;; dbindex.dsl)
-(define (htmlindexterm)
-  (let* ((attr    (gi (current-node)))
-         (content (data (current-node)))
-         (string  (strip (normalize-whitespace content))) ;; changed
-         (sortas  (attribute-string (normalize "sortas"))))
-    (make sequence
-      (make formatting-instruction data: attr)
-      (if sortas
-          (make sequence
-            (make formatting-instruction data: "[")
-            (make formatting-instruction data: sortas)
-            (make formatting-instruction data: "]"))
-          (empty-sosofo))
-      (make formatting-instruction data: " ")
-      (make formatting-instruction data: string)
-      (htmlnewline))))
-
-(define ($html-body-start$)
-        (if website-build
-            (make empty-element gi: "!--#include virtual=\"/resources/docs-header.html\"--")
-            (empty-sosofo)))
-
-(define ($html-body-end$)
-        (if website-build
-            (make empty-element gi: "!--#include virtual=\"/resources/docs-footer.html\"--")
-            (empty-sosofo)))
-
-]]> <!-- %output-html -->
-
-
-<!-- Print output customization .................................... -->
-
-<![ %output-print; [
-
-(define %section-autolabel%     #t)
-(define %default-quadding%      'justify)
-
-;; Don't know how well hyphenation works with other backends.  Might
-;; turn this on if desired.
-(define %hyphenation%
-  (if tex-backend #t #f))
-
-;; Put footnotes at the bottom of the page (rather than end of
-;; section), and put the URLs of links into footnotes.
-;;
-;; bop-footnotes only works with TeX, otherwise it's ignored.  But
-;; when both of these are #t and TeX is used, you need at least
-;; stylesheets 1.73 because otherwise you don't get any footnotes at
-;; all for the links.
-(define bop-footnotes           #t)
-(define %footnote-ulinks%       #t)
-
-(define %refentry-new-page%     #t)
-(define %refentry-keep%         #f)
-
-;; Disabled because of TeX problems
-;; (http://archives.postgresql.org/pgsql-docs/2007-12/msg00056.php)
-(define ($generate-book-lot-list$) '())
-
-;; Indentation of verbatim environments.  (This should really be done
-;; with start-indent in DSSSL.)
-;; Use of indentation in this area exposes a bug in openjade,
-;; http://archives.postgresql.org/pgsql-docs/2006-12/msg00064.php
-;; (define %indent-programlisting-lines% "    ")
-;; (define %indent-screen-lines% "    ")
-;; (define %indent-synopsis-lines% "    ")
-
-
-;; Default graphic format: Jadetex wants eps, pdfjadetex wants pdf.
-;; (Note that pdfjadetex will not accept eps, that's why we need to
-;; create a different .tex file for each.)  What works with RTF?
-
-(define texpdf-output #f) ;; override from command line
-
-(define %graphic-default-extension%
-  (cond (tex-backend (if texpdf-output "pdf" "eps"))
-        (rtf-backend "gif")
-        (else "XXX")))
-
-;; Need to add pdf here so that the above works.  Default setup
-;; doesn't know about PDF.
-(define preferred-mediaobject-extensions
-  (list "eps" "ps" "jpg" "jpeg" "pdf" "png"))
-
-
-;; Don't show links when citing a bibliography entry.  This fouls up
-;; the footnumber counting.  To get the link, one can still look into
-;; the bibliography itself.
-(mode xref-title-mode
-  (element ulink
-    (process-children)))
-
-
-;; Format legalnotice justified and with space between paragraphs.
-(mode book-titlepage-verso-mode
-  (element (legalnotice para)
-    (make paragraph
-      use: book-titlepage-verso-style   ;; alter this if ever it needs to appear elsewhere
-      quadding: %default-quadding%
-      line-spacing: (* 0.8 (inherited-line-spacing))
-      font-size: (* 0.8 (inherited-font-size))
-      space-before: (* 0.8 %para-sep%)
-      space-after: (* 0.8 %para-sep%)
-      first-line-start-indent: (if (is-first-para)
-                                   (* 0.8 %para-indent-firstpara%)
-                                   (* 0.8 %para-indent%))
-      (process-children))))
-
-
-;; Fix spacing problems in variablelists
-
-(element (varlistentry term)
-  (make paragraph
-    space-before: (if (first-sibling?)
-                      %para-sep%
-                      0pt)
-    keep-with-next?: #t
-    (process-children)))
-
-(define %varlistentry-indent% 2em)
-
-(element (varlistentry listitem)
-  (make sequence
-    start-indent: (+ (inherited-start-indent) %varlistentry-indent%)
-    (process-children)))
-
-
-;; Whitespace fixes for itemizedlists and orderedlists
-
-(define (process-listitem-content)
-  (if (absolute-first-sibling?)
-      (make sequence
-        (process-children-trim))
-      (next-match)))
-
-
-;; Default stylesheets format simplelists as tables.  This spells
-;; trouble for Jade.  So we just format them as plain lines.
-
-(define %simplelist-indent% 1em)
-
-(define (my-simplelist-vert members)
-  (make display-group
-    space-before: %para-sep%
-    space-after: %para-sep%
-    start-indent: (+ %simplelist-indent% (inherited-start-indent))
-    (process-children)))
-
-(element simplelist
-  (let ((type (attribute-string (normalize "type")))
-        (cols (if (attribute-string (normalize "columns"))
-                  (if (> (string->number (attribute-string (normalize "columns"))) 0)
-                      (string->number (attribute-string (normalize "columns")))
-                      1)
-                  1))
-        (members (select-elements (children (current-node)) (normalize "member"))))
-    (cond
-       ((equal? type (normalize "inline"))
-        (if (equal? (gi (parent (current-node)))
-                    (normalize "para"))
-            (process-children)
-            (make paragraph
-              space-before: %para-sep%
-              space-after: %para-sep%
-              start-indent: (inherited-start-indent))))
-       ((equal? type (normalize "vert"))
-        (my-simplelist-vert members))
-       ((equal? type (normalize "horiz"))
-        (simplelist-table 'row    cols members)))))
-
-(element member
-  (let ((type (inherited-attribute-string (normalize "type"))))
-    (cond
-     ((equal? type (normalize "inline"))
-      (make sequence
-        (process-children)
-        (if (not (last-sibling?))
-            (literal ", ")
-            (literal ""))))
-      ((equal? type (normalize "vert"))
-       (make paragraph
-         space-before: 0pt
-         space-after: 0pt))
-      ((equal? type (normalize "horiz"))
-       (make paragraph
-         quadding: 'start
-         (process-children))))))
-
-
-;; Jadetex doesn't handle links to the content of tables, so
-;; indexterms that point to table entries will go nowhere.  We fix
-;; this by pointing the index entry to the table itself instead, which
-;; should be equally useful in practice.
-
-(define (find-parent-table nd)
-  (let ((table (ancestor-member nd ($table-element-list$))))
-    (if (node-list-empty? table)
-        nd
-        table)))
-
-;; (The function below overrides the one in print/dbindex.dsl.)
-
-(define (indexentry-link nd)
-  (let* ((id        (attribute-string (normalize "role") nd))
-         (prelim-target (find-indexterm id))
-         (target    (find-parent-table prelim-target))
-         (preferred (not (node-list-empty?
-                          (select-elements (children (current-node))
-                                           (normalize "emphasis")))))
-         (sosofo    (if (node-list-empty? target)
-                        (literal "?")
-                        (make link
-                          destination: (node-list-address target)
-                          (with-mode toc-page-number-mode
-                            (process-node-list target))))))
-    (if preferred
-        (make sequence
-          font-weight: 'bold
-          sosofo)
-        sosofo)))
-
-
-;; By default, the part and reference title pages get wrong page
-;; numbers: The first title page gets roman numerals carried over from
-;; preface/toc -- we want Arabic numerals.  We also need to make sure
-;; that page-number-restart is set of #f explicitly, because otherwise
-;; it will carry over from the previous component, which is not good.
-;;
-;; (This looks worse than it is.  It's copied from print/dbttlpg.dsl
-;; and common/dbcommon.dsl and modified in minor detail.)
-
-(define (first-part?)
-  (let* ((book (ancestor (normalize "book")))
-         (nd   (ancestor-member (current-node)
-                                (append
-                                 (component-element-list)
-                                 (division-element-list))))
-         (bookch (children book)))
-    (let loop ((nl bookch))
-      (if (node-list-empty? nl)
-          #f
-          (if (equal? (gi (node-list-first nl)) (normalize "part"))
-              (if (node-list=? (node-list-first nl) nd)
-                  #t
-                  #f)
-              (loop (node-list-rest nl)))))))
-
-(define (first-reference?)
-  (let* ((book (ancestor (normalize "book")))
-         (nd   (ancestor-member (current-node)
-                                (append
-                                 (component-element-list)
-                                 (division-element-list))))
-         (bookch (children book)))
-    (let loop ((nl bookch))
-      (if (node-list-empty? nl)
-          #f
-          (if (equal? (gi (node-list-first nl)) (normalize "reference"))
-              (if (node-list=? (node-list-first nl) nd)
-                  #t
-                  #f)
-              (loop (node-list-rest nl)))))))
-
-
-(define (part-titlepage elements #!optional (side 'recto))
-  (let ((nodelist (titlepage-nodelist
-                   (if (equal? side 'recto)
-                       (reference-titlepage-recto-elements)
-                       (reference-titlepage-verso-elements))
-                   elements))
-        ;; partintro is a special case...
-        (partintro (node-list-first
-                    (node-list-filter-by-gi elements (list (normalize "partintro"))))))
-    (if (part-titlepage-content? elements side)
-        (make simple-page-sequence
-          page-n-columns: %titlepage-n-columns%
-          ;; Make sure that page number format is correct.
-          page-number-format: ($page-number-format$)
-          ;; Make sure that the page number is set to 1 if this is the
-          ;; first part in the book
-          page-number-restart?: (first-part?)
-          input-whitespace-treatment: 'collapse
-          use: default-text-style
-
-          ;; This hack is required for the RTF backend. If an external-graphic
-          ;; is the first thing on the page, RTF doesn't seem to do the right
-          ;; thing (the graphic winds up on the baseline of the first line
-          ;; of the page, left justified).  This "one point rule" fixes
-          ;; that problem.
-          (make paragraph
-            line-spacing: 1pt
-            (literal ""))
-
-          (let loop ((nl nodelist) (lastnode (empty-node-list)))
-            (if (node-list-empty? nl)
-                (empty-sosofo)
-                (make sequence
-                  (if (or (node-list-empty? lastnode)
-                          (not (equal? (gi (node-list-first nl))
-                                       (gi lastnode))))
-                      (part-titlepage-before (node-list-first nl) side)
-                      (empty-sosofo))
-                  (cond
-                   ((equal? (gi (node-list-first nl)) (normalize "subtitle"))
-                    (part-titlepage-subtitle (node-list-first nl) side))
-                   ((equal? (gi (node-list-first nl)) (normalize "title"))
-                    (part-titlepage-title (node-list-first nl) side))
-                   (else
-                    (part-titlepage-default (node-list-first nl) side)))
-                  (loop (node-list-rest nl) (node-list-first nl)))))
-
-          (if (and %generate-part-toc%
-                   %generate-part-toc-on-titlepage%
-                   (equal? side 'recto))
-              (make display-group
-                (build-toc (current-node)
-                           (toc-depth (current-node))))
-              (empty-sosofo))
-
-          ;; PartIntro is a special case
-          (if (and (equal? side 'recto)
-                   (not (node-list-empty? partintro))
-                   %generate-partintro-on-titlepage%)
-              ($process-partintro$ partintro #f)
-              (empty-sosofo)))
-
-        (empty-sosofo))))
-
-
-(define (reference-titlepage elements #!optional (side 'recto))
-  (let ((nodelist (titlepage-nodelist
-                   (if (equal? side 'recto)
-                       (reference-titlepage-recto-elements)
-                       (reference-titlepage-verso-elements))
-                   elements))
-        ;; partintro is a special case...
-        (partintro (node-list-first
-                    (node-list-filter-by-gi elements (list (normalize "partintro"))))))
-    (if (reference-titlepage-content? elements side)
-        (make simple-page-sequence
-          page-n-columns: %titlepage-n-columns%
-          ;; Make sure that page number format is correct.
-          page-number-format: ($page-number-format$)
-          ;; Make sure that the page number is set to 1 if this is the
-          ;; first part in the book
-          page-number-restart?: (first-reference?)
-          input-whitespace-treatment: 'collapse
-          use: default-text-style
-
-          ;; This hack is required for the RTF backend. If an external-graphic
-          ;; is the first thing on the page, RTF doesn't seem to do the right
-          ;; thing (the graphic winds up on the baseline of the first line
-          ;; of the page, left justified).  This "one point rule" fixes
-          ;; that problem.
-          (make paragraph
-            line-spacing: 1pt
-            (literal ""))
-
-          (let loop ((nl nodelist) (lastnode (empty-node-list)))
-            (if (node-list-empty? nl)
-                (empty-sosofo)
-                (make sequence
-                  (if (or (node-list-empty? lastnode)
-                          (not (equal? (gi (node-list-first nl))
-                                       (gi lastnode))))
-                      (reference-titlepage-before (node-list-first nl) side)
-                      (empty-sosofo))
-                  (cond
-                   ((equal? (gi (node-list-first nl)) (normalize "author"))
-                    (reference-titlepage-author (node-list-first nl) side))
-                   ((equal? (gi (node-list-first nl)) (normalize "authorgroup"))
-                    (reference-titlepage-authorgroup (node-list-first nl) side))
-                   ((equal? (gi (node-list-first nl)) (normalize "corpauthor"))
-                    (reference-titlepage-corpauthor (node-list-first nl) side))
-                   ((equal? (gi (node-list-first nl)) (normalize "editor"))
-                    (reference-titlepage-editor (node-list-first nl) side))
-                   ((equal? (gi (node-list-first nl)) (normalize "subtitle"))
-                    (reference-titlepage-subtitle (node-list-first nl) side))
-                   ((equal? (gi (node-list-first nl)) (normalize "title"))
-                    (reference-titlepage-title (node-list-first nl) side))
-                   (else
-                    (reference-titlepage-default (node-list-first nl) side)))
-                  (loop (node-list-rest nl) (node-list-first nl)))))
-
-          (if (and %generate-reference-toc%
-                   %generate-reference-toc-on-titlepage%
-                   (equal? side 'recto))
-              (make display-group
-                (build-toc (current-node)
-                           (toc-depth (current-node))))
-              (empty-sosofo))
-
-          ;; PartIntro is a special case
-          (if (and (equal? side 'recto)
-                   (not (node-list-empty? partintro))
-                   %generate-partintro-on-titlepage%)
-              ($process-partintro$ partintro #f)
-              (empty-sosofo)))
-
-        (empty-sosofo))))
-
-]]> <!-- %output-print -->
-
-
-<!-- Plain text output customization ............................... -->
-
-<!--
-This is used for making the INSTALL file and others.  We customize the
-HTML stylesheets to be suitable for dumping plain text (via Netscape,
-Lynx, or similar).
--->
-
-<![ %output-text; [
-
-(define %section-autolabel% #f)
-(define %chapter-autolabel% #f)
-(define $generate-chapter-toc$ (lambda () #f))
-
-;; For text output, produce "ASCII markup" for emphasis and such.
-
-(define ($asterix-seq$ #!optional (sosofo (process-children)))
-  (make sequence
-    (literal "*")
-    sosofo
-    (literal "*")))
-
-(define ($dquote-seq$ #!optional (sosofo (process-children)))
-  (make sequence
-    (literal (gentext-start-quote))
-    sosofo
-    (literal (gentext-end-quote))))
-
-(element (para command) ($dquote-seq$))
-(element (para emphasis) ($asterix-seq$))
-(element (para filename) ($dquote-seq$))
-(element (para option) ($dquote-seq$))
-(element (para replaceable) ($dquote-seq$))
-(element (para userinput) ($dquote-seq$))
-
-]]> <!-- %output-text -->
-
-  </style-specification-body>
- </style-specification>
-
- <external-specification id="docbook" document="dbstyle">
-</style-sheet>

doc/stylesheet.xsl

@@ -1,174 +0,0 @@
-<?xml version='1.0'?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
-                version='1.0'
-                xmlns="http://www.w3.org/TR/xhtml1/transitional"
-                exclude-result-prefixes="#default">
-
-<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl"/>
-<xsl:include href="stylesheet-common.xsl" />
-<xsl:include href="stylesheet-html-common.xsl" />
-<xsl:include href="stylesheet-speedup-xhtml.xsl" />
-
-
-<!-- Parameters -->
-<xsl:param name="base.dir" select="'html/'"></xsl:param>
-<xsl:param name="use.id.as.filename" select="'1'"></xsl:param>
-<xsl:param name="generate.legalnotice.link" select="1"></xsl:param>
-<xsl:param name="chunk.first.sections" select="1"/>
-<xsl:param name="chunk.quietly" select="1"></xsl:param>
-<xsl:param name="admon.style"></xsl:param>  <!-- handled by CSS stylesheet -->
-
-<xsl:param name="website.stylesheet" select="0"/>
-
-<xsl:param name="html.stylesheet">
-  <xsl:choose>
-    <xsl:when test="$website.stylesheet = 0">stylesheet.css</xsl:when>
-    <xsl:otherwise>https://www.postgresql.org/media/css/docs.css</xsl:otherwise>
-  </xsl:choose>
-</xsl:param>
-
-
-<!-- strip directory name from image filerefs -->
-<xsl:template match="imagedata/@fileref">
- <xsl:value-of select="substring-after(., '/')"/>
-</xsl:template>
-
-
-<!--
-Customization of header
-- add Up and Home links
-- add tool tips to links
-
-(overrides html/chunk-common.xsl)
--->
-<xsl:template name="header.navigation">
-  <xsl:param name="prev" select="/foo"/>
-  <xsl:param name="next" select="/foo"/>
-  <xsl:param name="nav.context"/>
-
-  <xsl:variable name="home" select="/*[1]"/>
-  <xsl:variable name="up" select="parent::*"/>
-
-  <xsl:variable name="row1" select="$navig.showtitles != 0"/>
-  <xsl:variable name="row2" select="count($prev) &gt; 0
-                                    or (count($up) &gt; 0
-                                        and generate-id($up) != generate-id($home)
-                                        and $navig.showtitles != 0)
-                                    or count($next) &gt; 0"/>
-
-  <xsl:if test="$suppress.navigation = '0' and $suppress.header.navigation = '0'">
-    <div class="navheader">
-      <xsl:if test="$row1 or $row2">
-        <table width="100%" summary="Navigation header">
-          <xsl:if test="$row1">
-            <tr>
-              <th colspan="5" align="center">
-                <xsl:apply-templates select="." mode="object.title.markup"/>
-              </th>
-            </tr>
-          </xsl:if>
-
-          <xsl:if test="$row2">
-            <tr>
-              <td width="10%" align="{$direction.align.start}">
-                <xsl:if test="count($prev)>0">
-                  <a accesskey="p">
-                    <xsl:attribute name="href">
-                      <xsl:call-template name="href.target">
-                        <xsl:with-param name="object" select="$prev"/>
-                      </xsl:call-template>
-                    </xsl:attribute>
-                    <xsl:attribute name="title">
-                      <xsl:apply-templates select="$prev" mode="object.title.markup"/>
-                    </xsl:attribute>
-                    <xsl:call-template name="navig.content">
-                      <xsl:with-param name="direction" select="'prev'"/>
-                    </xsl:call-template>
-                  </a>
-                </xsl:if>
-                <xsl:text>&#160;</xsl:text>
-              </td>
-              <td width="10%" align="{$direction.align.start}">
-                <xsl:choose>
-                  <xsl:when test="count($up)&gt;0
-                                  and generate-id($up) != generate-id($home)">
-                    <a accesskey="u">
-                      <xsl:attribute name="href">
-                        <xsl:call-template name="href.target">
-                          <xsl:with-param name="object" select="$up"/>
-                        </xsl:call-template>
-                      </xsl:attribute>
-                      <xsl:attribute name="title">
-                        <xsl:apply-templates select="$up" mode="object.title.markup"/>
-                      </xsl:attribute>
-                      <xsl:call-template name="navig.content">
-                        <xsl:with-param name="direction" select="'up'"/>
-                      </xsl:call-template>
-                    </a>
-                  </xsl:when>
-                  <xsl:otherwise>&#160;</xsl:otherwise>
-                </xsl:choose>
-              </td>
-              <th width="60%" align="center">
-                <xsl:choose>
-                  <xsl:when test="count($up) > 0
-                                  and generate-id($up) != generate-id($home)
-                                  and $navig.showtitles != 0">
-                    <xsl:apply-templates select="$up" mode="object.title.markup"/>
-                  </xsl:when>
-                  <xsl:otherwise>&#160;</xsl:otherwise>
-                </xsl:choose>
-              </th>
-              <td width="10%" align="{$direction.align.end}">
-                <xsl:choose>
-                  <xsl:when test="$home != . or $nav.context = 'toc'">
-                    <a accesskey="h">
-                      <xsl:attribute name="href">
-                        <xsl:call-template name="href.target">
-                          <xsl:with-param name="object" select="$home"/>
-                        </xsl:call-template>
-                      </xsl:attribute>
-                    <xsl:attribute name="title">
-                      <xsl:apply-templates select="$home" mode="object.title.markup"/>
-                    </xsl:attribute>
-                      <xsl:call-template name="navig.content">
-                        <xsl:with-param name="direction" select="'home'"/>
-                      </xsl:call-template>
-                    </a>
-                    <xsl:if test="$chunk.tocs.and.lots != 0 and $nav.context != 'toc'">
-                      <xsl:text>&#160;|&#160;</xsl:text>
-                    </xsl:if>
-                  </xsl:when>
-                  <xsl:otherwise>&#160;</xsl:otherwise>
-                </xsl:choose>
-              </td>
-              <td width="10%" align="{$direction.align.end}">
-                <xsl:text>&#160;</xsl:text>
-                <xsl:if test="count($next)>0">
-                  <a accesskey="n">
-                    <xsl:attribute name="href">
-                      <xsl:call-template name="href.target">
-                        <xsl:with-param name="object" select="$next"/>
-                      </xsl:call-template>
-                    </xsl:attribute>
-                    <xsl:attribute name="title">
-                      <xsl:apply-templates select="$next" mode="object.title.markup"/>
-                    </xsl:attribute>
-                    <xsl:call-template name="navig.content">
-                      <xsl:with-param name="direction" select="'next'"/>
-                    </xsl:call-template>
-                  </a>
-                </xsl:if>
-              </td>
-            </tr>
-          </xsl:if>
-        </table>
-      </xsl:if>
-      <xsl:if test="$header.rule != 0">
-        <hr/>
-      </xsl:if>
-    </div>
-  </xsl:if>
-</xsl:template>
-
-</xsl:stylesheet>

doc/switchover.xml

@@ -1,427 +0,0 @@
-<chapter id="performing-switchover" xreflabel="Performing a switchover with repmgr">
- <title>Performing a switchover with repmgr</title>
-
- <indexterm>
-  <primary>switchover</primary>
- </indexterm>
-
- <para>
-  A typical use-case for replication is a combination of primary and standby
-  server, with the standby serving as a backup which can easily be activated
-  in case of a problem with the primary. Such an unplanned failover would
-  normally be handled by promoting the standby, after which an appropriate
-  action must be taken to restore the old primary.
- </para>
- <para>
-  In some cases however it's desirable to promote the standby in a planned
-  way, e.g. so maintenance can be performed on the primary; this kind of switchover
-  is supported by the <xref linkend="repmgr-standby-switchover"/> command.
- </para>
- <para>
-  <command>repmgr standby switchover</command> differs from other &repmgr;
-  actions in that it also performs actions on other servers (the demotion
-  candidate, and optionally any other servers which are to follow the new primary),
-  which means passwordless SSH access is required to those servers from the one where
-  <command>repmgr standby switchover</command> is executed.
- </para>
- <note>
-  <simpara>
-   <command>repmgr standby switchover</command> performs a relatively complex
-   series of operations on two servers, and should therefore be performed after
-   careful preparation and with adequate attention. In particular you should
-   be confident that your network environment is stable and reliable.
-  </simpara>
-  <simpara>
-   Additionally you should be sure that the current primary can be shut down
-   quickly and cleanly. In particular, access from applications should be
-   minimalized or preferably blocked completely. Also be aware that if there
-   is a backlog of files waiting to be archived, PostgreSQL will not shut
-   down until archiving completes.
-  </simpara>
-  <simpara>
-    We recommend running <command>repmgr standby switchover</command> at the
-    most verbose logging level (<literal>--log-level=DEBUG --verbose</literal>)
-    and capturing all output to assist troubleshooting any problems.
-  </simpara>
-  <simpara>
-   Please also read carefully the sections <xref linkend="preparing-for-switchover"/> and
-   <xref linkend="switchover-caveats"/> below.
-  </simpara>
- </note>
-
- <sect1 id="preparing-for-switchover" xreflabel="Preparing for switchover">
-   <title>Preparing for switchover</title>
-
-   <indexterm>
-     <primary>switchover</primary>
-     <secondary>preparation</secondary>
-   </indexterm>
-
-   <para>
-    As mentioned in the previous section, success of the switchover operation depends on
-    &repmgr; being able to shut down the current primary server quickly and cleanly.
-   </para>
-
-   <para>
-     Ensure that the promotion candidate has sufficient free walsenders available
-     (PostgreSQL configuration item <varname>max_wal_senders</varname>), and if replication
-     slots are in use, at least one free slot is available for the demotion candidate (
-     PostgreSQL configuration item <varname>max_replication_slots</varname>).
-   </para>
-
-   <para>
-     Ensure that a passwordless SSH connection is possible from the promotion candidate
-     (standby) to the demotion candidate (current primary). If <literal>--siblings-follow</literal>
-     will be used, ensure that passwordless SSH connections are possible from the
-     promotion candidate to all nodes attached to the demotion candidate
-     (including the witness server, if in use).
-   </para>
-
-   <note>
-     <simpara>
-       &repmgr; expects to find the &repmgr; binary in the same path on the remote
-       server as on the local server.
-     </simpara>
-   </note>
-
-   <para>
-    Double-check which commands will be used to stop/start/restart the current
-    primary; this can be done by e.g. executing <command><link linkend="repmgr-node-service">repmgr node service</link></command>
-    on the current primary:
-    <programlisting>
-     repmgr -f /etc/repmgr.conf node service --list-actions --action=stop
-     repmgr -f /etc/repmgr.conf node service --list-actions --action=start
-     repmgr -f /etc/repmgr.conf node service --list-actions --action=restart</programlisting>
-
-   </para>
-
-   <para>
-     These commands can be defined in <filename>repmgr.conf</filename> with
-     <option>service_start_command</option>, <option>service_stop_command</option>
-     and <option>service_restart_command</option>.
-   </para>
-
-   <important>
-     <para>
-       If &repmgr; is installed from a package. you should set these commands
-       to use the appropriate service commands defined by the package/operating
-       system as these will ensure PostgreSQL is stopped/started properly
-       taking into account configuration and log file locations etc.
-     </para>
-     <para>
-       If the <option>service_*_command</option> options aren't defined, &repmgr; will
-       fall back to using <application>pg_ctl</application> to stop/start/restart
-       PostgreSQL, which may not work properly, particularly when executed on a remote
-       server.
-     </para>
-     <para>
-       For more details, see <xref linkend="configuration-file-service-commands"/>.
-     </para>
-   </important>
-
-   <note>
-    <para>
-     On <literal>systemd</literal> systems we strongly recommend using the appropriate
-     <command>systemctl</command> commands (typically run via <command>sudo</command>) to ensure
-     <literal>systemd</literal> is informed about the status of the PostgreSQL service.
-    </para>
-    <para>
-     If using <command>sudo</command> for the <command>systemctl</command> calls, make sure the
-     <command>sudo</command> specification doesn't require a real tty for the user. If not set
-     this way, <command>repmgr</command> will fail to stop the primary.
-    </para>
-    <para>
-      See the <xref linkend="configuration-file-service-commands"/> documentation section for further details.
-    </para>
-   </note>
-
-   <para>
-     Check that access from applications is minimalized or preferably blocked
-     completely, so applications are not unexpectedly interrupted.
-   </para>
-
-   <note>
-     <para>
-       If an exclusive backup is running on the current primary, or if WAL replay is paused on the standby,
-       &repmgr; will <emphasis>not</emphasis> perform the switchover.
-     </para>
-   </note>
-
-   <para>
-     Check there is no significant replication lag on standbys attached to the
-     current primary.
-   </para>
-
-   <para>
-    If WAL file archiving is set up, check that there is no backlog of files waiting
-    to be archived, as PostgreSQL will not finally shut down until all of these have been
-    archived. If there is a backlog exceeding <varname>archive_ready_warning</varname> WAL files,
-    &repmgr; will emit a warning before attempting to perform a switchover; you can also check
-    manually with <command>repmgr node check --archive-ready</command>.
-   </para>
-
-    <note>
-      <para>
-        From <link linkend="release-4.2">repmgr 4.2</link>, &repmgr; will instruct any running
-        &repmgrd; instances to pause operations while the switchover
-        is being carried out, to prevent &repmgrd; from
-        unintentionally promoting a node. For more details, see <xref linkend="repmgrd-pausing"/>.
-      </para>
-      <para>
-        Users of &repmgr; versions prior to 4.2 should ensure that &repmgrd;
-        is not running on any nodes while a switchover is being executed.
-      </para>
-    </note>
-
-
-   <para>
-    Finally, consider executing <command>repmgr standby switchover</command> with the
-    <literal>--dry-run</literal> option; this will perform any necessary checks and inform you about
-    success/failure, and stop before the first actual command is run (which would be the shutdown of the
-    current primary). Example output:
-    <programlisting>
-      $ repmgr standby switchover -f /etc/repmgr.conf --siblings-follow --dry-run
-      NOTICE: checking switchover on node "node2" (ID: 2) in --dry-run mode
-      INFO: SSH connection to host "node1" succeeded
-      INFO: archive mode is "off"
-      INFO: replication lag on this standby is 0 seconds
-      INFO: all sibling nodes are reachable via SSH
-      NOTICE: local node "node2" (ID: 2) will be promoted to primary; current primary "node1" (ID: 1) will be demoted to standby
-      INFO: following shutdown command would be run on node "node1":
-        "pg_ctl -l /var/log/postgresql/startup.log -D '/var/lib/postgresql/data' -m fast -W stop"
-      INFO: parameter "shutdown_check_timeout" is set to 60 seconds
-    </programlisting>
-   </para>
-
-   <important>
-     <para>
-       Be aware that <option>--dry-run</option> checks the prerequisites
-       for performing the switchover and some basic sanity checks on the
-       state of the database which might effect the switchover operation
-       (e.g. replication lag); it cannot however guarantee the switchover
-       operation will succeed. In particular, if the current primary
-       does not shut down cleanly, &repmgr; will not be able to reliably
-       execute the switchover (as there would be a danger of divergence
-       between the former and new primary nodes).
-     </para>
-   </important>
-
-
-   <note>
-     <simpara>
-       See <xref linkend="repmgr-standby-switchover"/> for a full list of available
-       command line options and <filename>repmgr.conf</filename> settings relevant
-       to performing a switchover.
-     </simpara>
-   </note>
-
-   <sect2 id="switchover-pg-rewind" xreflabel="Switchover and pg_rewind">
-    <title>Switchover and pg_rewind</title>
-
-    <indexterm>
-      <primary>pg_rewind</primary>
-      <secondary>using with "repmgr standby switchover"</secondary>
-    </indexterm>
-    <para>
-      If the demotion candidate does not shut down smoothly or cleanly, there's a risk it
-      will have a slightly divergent timeline and will not be able to attach to the new
-      primary. To fix this situation without needing to reclone the old primary, it's
-      possible to use the <application>pg_rewind</application> utility, which will usually be
-      able to resync the two servers.
-    </para>
-    <para>
-      To have &repmgr; execute <application>pg_rewind</application> if it detects this
-      situation after promoting the new primary, add the <option>--force-rewind</option>
-      option.
-    </para>
-    <note>
-      <simpara>
-        If &repmgr; detects a situation where it needs to execute <application>pg_rewind</application>,
-        it will execute a <literal>CHECKPOINT</literal> on the new primary before executing
-        <application>pg_rewind</application>.
-      </simpara>
-    </note>
-    <para>
-      For more details on <application>pg_rewind</application>, see section <xref linkend="repmgr-node-rejoin-pg-rewind"/>
-      in the <link linkend="repmgr-node-rejoin"><command>repmgr node rejoin</command></link> documentation and
-      the PostgreSQL documentation at
-      <ulink url="https://www.postgresql.org/docs/current/app-pgrewind.html">https://www.postgresql.org/docs/current/app-pgrewind.html</ulink>.
-    </para>
-
-  </sect2>
-
-
- </sect1>
-
- <sect1 id="switchover-execution" xreflabel="Executing the switchover command">
-  <title>Executing the switchover command</title>
-
-  <indexterm>
-   <primary>switchover</primary>
-    <secondary>execution</secondary>
-  </indexterm>
-  <para>
-   To demonstrate switchover, we will assume a replication cluster with a
-   primary (<literal>node1</literal>) and one standby (<literal>node2</literal>);
-   after the switchover <literal>node2</literal> should become the primary with
-   <literal>node1</literal> following it.
-  </para>
-  <para>
-   The switchover command must be run from the standby which is to be promoted,
-   and in its simplest form looks like this:
-   <programlisting>
-    $ repmgr -f /etc/repmgr.conf standby switchover
-    NOTICE: executing switchover on node "node2" (ID: 2)
-    INFO: searching for primary node
-    INFO: checking if node 1 is primary
-    INFO: current primary node is 1
-    INFO: SSH connection to host "node1" succeeded
-    INFO: archive mode is "off"
-    INFO: replication lag on this standby is 0 seconds
-    NOTICE: local node "node2" (ID: 2) will be promoted to primary; current primary "node1" (ID: 1) will be demoted to standby
-    NOTICE: stopping current primary node "node1" (ID: 1)
-    NOTICE: issuing CHECKPOINT
-    DETAIL: executing server command "pg_ctl -l /var/log/postgres/startup.log -D '/var/lib/pgsql/data' -m fast -W stop"
-    INFO: checking primary status; 1 of 6 attempts
-    NOTICE: current primary has been cleanly shut down at location 0/3001460
-    NOTICE: promoting standby to primary
-    DETAIL: promoting server "node2" (ID: 2) using "pg_ctl -l /var/log/postgres/startup.log -w -D '/var/lib/pgsql/data' promote"
-    server promoting
-    NOTICE: STANDBY PROMOTE successful
-    DETAIL: server "node2" (ID: 2) was successfully promoted to primary
-    INFO: setting node 1's primary to node 2
-    NOTICE: starting server using  "pg_ctl -l /var/log/postgres/startup.log -w -D '/var/lib/pgsql/data' restart"
-    NOTICE: NODE REJOIN successful
-    DETAIL: node 1 is now attached to node 2
-    NOTICE: switchover was successful
-    DETAIL: node "node2" is now primary
-    NOTICE: STANDBY SWITCHOVER is complete
-   </programlisting>
-  </para>
-  <para>
-   The old primary is now replicating as a standby from the new primary, and the
-   cluster status will now look like this:
-   <programlisting>
-    $ repmgr -f /etc/repmgr.conf cluster show
-     ID | Name  | Role    | Status    | Upstream | Location | Connection string
-    ----+-------+---------+-----------+----------+----------+--------------------------------------
-     1  | node1 | standby |   running | node2    | default  | host=node1 dbname=repmgr user=repmgr
-     2  | node2 | primary | * running |          | default  | host=node2 dbname=repmgr user=repmgr
-   </programlisting>
-  </para>
-  <para>
-    If &repmgrd; is in use, it's worth double-checking that
-    all nodes are unpaused by executing
-    <command><link linkend="repmgr-service-status">repmgr service status</link></command>
-    (&repmgr; 4.2 - 4.4: <command><link linkend="repmgr-service-status">repmgr daemon status</link></command>).
-  </para>
-
-   <note>
-     <para>
-       Users of &repmgr; versions prior to 4.2 will need to manually restart &repmgrd;
-       on all nodes after the switchover is completed.
-     </para>
-    </note>
-
- </sect1>
-
-
- <sect1 id="switchover-caveats" xreflabel="Caveats">
-  <title>Caveats</title>
-  <indexterm>
-   <primary>switchover</primary>
-    <secondary>caveats</secondary>
-  </indexterm>
-  <para>
-   <itemizedlist spacing="compact" mark="bullet">
-    <listitem>
-     <simpara>
-      If using PostgreSQL 9.4, you should ensure that the shutdown command
-      is configured to use PostgreSQL's <varname>fast</varname> shutdown mode (the default in 9.5
-      and later). If relying on <command>pg_ctl</command> to perform database server operations,
-      you should include <literal>-m fast</literal> in <varname>pg_ctl_options</varname>
-      in <filename>repmgr.conf</filename>.
-     </simpara>
-    </listitem>
-    <listitem>
-     <simpara>
-      <command>pg_rewind</command> *requires* that either <varname>wal_log_hints</varname> is enabled, or that
-      data checksums were enabled when the cluster was initialized. See the
-      <ulink url="https://www.postgresql.org/docs/current/app-pgrewind.html">pg_rewind documentation</ulink>
-      for details.
-     </simpara>
-    </listitem>
-   </itemizedlist>
-  </para>
- </sect1>
-
- <sect1 id="switchover-troubleshooting" xreflabel="Troubleshooting">
-   <title>Troubleshooting switchover issues</title>
-
-   <indexterm>
-     <primary>switchover</primary>
-     <secondary>troubleshooting</secondary>
-   </indexterm>
-
-   <para>
-     As <link linkend="performing-switchover">emphasised previously</link>, performing a switchover
-     is a non-trivial operation and there are a number of potential issues which can occur.
-     While &repmgr; attempts to perform sanity checks, there's no guaranteed way of determining the success of
-     a switchover without actually carrying it out.
-   </para>
-
-   <sect2 id="switchover-troubleshooting-primary-shutdown">
-     <title>Demotion candidate (old primary) does not shut down</title>
-     <para>
-       &repmgr; may abort a switchover with a message like:
-       <programlisting>
-ERROR: shutdown of the primary server could not be confirmed
-HINT: check the primary server status before performing any further actions</programlisting>
-     </para>
-     <para>
-       This means the shutdown of the old primary has taken longer than &repmgr; expected,
-       and it has given up waiting.
-     </para>
-     <para>
-       In this case, check the PostgreSQL log on the primary server to see what is going
-       on. It's entirely possible the shutdown process is just taking longer than the
-       timeout set by the configuration parameter <varname>shutdown_check_timeout</varname>
-       (default: 60 seconds), in which case you may need to adjust this parameter.
-     </para>
-     <note>
-       <para>
-         Note that <varname>shutdown_check_timeout</varname> is set on the node where
-         <command>repmgr standby switchover</command> is executed (promotion candidate); setting it on the
-         demotion candidate (former primary) will have no effect.
-       </para>
-     </note>
-     <para>
-       If the primary server has shut down cleanly, and no other node has been promoted,
-       it is safe to restart it, in which case the replication cluster will be restored
-       to its original configuration.
-     </para>
-   </sect2>
-
-   <sect2 id="switchover-troubleshooting-exclusive-backup">
-     <title>Switchover aborts with an &quot;exclusive backup&quot; error</title>
-     <para>
-       &repmgr; may abort a switchover with a message like:
-       <programlisting>
-ERROR: unable to perform a switchover while primary server is in exclusive backup mode
-HINT: stop backup before attempting the switchover</programlisting>
-     </para>
-     <para>
-       This means an exclusive backup is running on the current primary; interrupting this
-       will not only abort the backup, but potentially leave the primary with an ambiguous
-       backup state.
-     </para>
-     <para>
-       To proceed, either wait until the backup has finished, or cancel it with the command
-       <command>SELECT pg_stop_backup()</command>. For more details see the PostgreSQL
-       documentation section
-       <ulink url="https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-LOWLEVEL-BASE-BACKUP-EXCLUSIVE">Making an exclusive low level backup</ulink>.
-     </para>
-   </sect2>
- </sect1>
-
-</chapter>

doc/upgrading-from-repmgr3.md

@@ -1,9 +1,121 @@
 Upgrading from repmgr 3
 =======================
 
-This document has been integrated into the main `repmgr` documentation
+The upgrade process consists of two steps:
-and is now located here:
 
-> [Upgrading from repmgr 3.x](https://repmgr.org/docs/current/upgrading-from-repmgr-3.html)
+    1) converting the repmgr.conf configuration files
+    2) upgrading the repmgr schema.
+
+Scripts are provided to assist both with converting repmgr.conf
+and upgrading the schema.
+
+Converting repmgr.conf configuration files
+------------------------------------------
+
+With a completely new repmgr version, we've taken the opportunity
+to rename some configuration items have had their names changed for
+clarity and consistency, both between the configuration file and
+the column names in `repmgr.nodes` (e.g. `node` → `node_id`), and
+also for consistency with PostgreSQL naming conventions
+(e.g. `loglevel` → `log_level`).
+
+Other configuration items have been changed to command line options,
+and vice-versa, e.g. to avoid hard-coding items such as a a node's
+upstream ID, which might change over time.
+
+`repmgr` will issue a warning about deprecated/altered options.
 
 
+### Changed parameters
+
+Following parameters have been added:
+
+    - `data_directory`: this is mandatory and must contain the path
+        to the node's data directory
+    - `monitoring_history`: this replaces the `repmgrd` command line
+        option `--monitoring-history`
+
+Following parameters have been renamed:
+
+    - `node` → `node_id`
+    - `loglevel` → `log_level`
+    - `logfacility` → `log_facility`
+    - `logfile` → `log_file`
+    - `master_reponse_timeout` → `async_query_timeout`
+
+Following parameters have been removed:
+
+    - `cluster` is no longer required and will be ignored.
+    - `upstream_node_id` is replaced by the command-line parameter
+         `--upstream-node-id`
+
+### Conversion script
+
+To assist with conversion of `repmgr.conf` files, a Perl script
+is provided in `contrib/convert-config.pl`. Use like this:
+
+    $ ./convert-config.pl /etc/repmgr.conf
+    node_id=2
+    node_name=node2
+    conninfo=host=localhost dbname=repmgr user=repmgr port=5602
+    pg_ctl_options='-l /tmp/postgres.5602.log'
+    pg_bindir=/home/barwick/devel/builds/HEAD/bin
+    rsync_options=--exclude=postgresql.local.conf --archive
+    log_level=DEBUG
+    pg_basebackup_options=--no-slot
+    data_directory=
+
+The converted file is printed to `STDOUT` and the original file is not
+changed.
+
+Please note that the parameter `data_directory` *must* be provided;
+if not already present, the conversion script will add an empty
+placeholder parameter.
+
+
+Upgrading the repmgr schema
+---------------------------
+
+Ensure `repmgrd` is not running, or any cron jobs which execute the
+`repmgr` binary.
+
+Install `repmgr4`; any `repmgr3` packages should be uninstalled
+(if not automatically installed already).
+
+### Manually create the repmgr extension
+
+In the database used by the existing `repmgr` configuration, execute:
+
+    CREATE EXTENSION repmgr FROM unpackaged;
+
+This will move and convert all objects from the existing schema
+into the new, standard `repmgr` schema.
+
+> *NOTE* there must be only one schema matching 'repmgr_%' in the
+> database, otherwise this step may not work.
+
+### Re-register each node
+
+This is necessary to update the `repmgr` metadata with some additional items.
+
+On the primary node, execute e.g.
+
+    repmgr primary register -f /etc/repmgr.conf --force
+
+On each standby node, execute e.g.
+
+    repmgr standby register -f /etc/repmgr.conf --force
+
+Check the data is updated as expected by examining the `repmgr.nodes` table;
+restart `repmgrd` if required.
+
+The original `repmgr_$cluster` schema can be dropped at any time.
+
+* * *
+
+> *TIP* If you don't care about any data from the existing `repmgr` installation,
+> (e.g. the contents of the `events` and `monitoring` tables), the manual
+> "CREATE EXTENSION" step can be skipped; just re-register each node, starting
+> with the primary node, and the `repmgr` extension will be automatically created.
+
+* * *

doc/upgrading-repmgr.xml

@@ -1,597 +0,0 @@
-<chapter id="upgrading-repmgr" xreflabel="Upgrading repmgr">
- <title>Upgrading repmgr</title>
-
- <indexterm>
-  <primary>upgrading</primary>
- </indexterm>
-
-
- <para>
-  &repmgr; is updated regularly with minor releases (e.g. 4.0.1 to 4.0.2)
-  containing bugfixes and other minor improvements. Any substantial new
-  functionality will be included in a major release (e.g. 4.0 to 4.1).
- </para>
-
- <sect1 id="upgrading-repmgr-extension" xreflabel="Upgrading repmgr 4.x and later">
-  <title>Upgrading repmgr 4.x and later</title>
-
-  <indexterm>
-   <primary>upgrading</primary>
-   <secondary>repmgr 4.x and later</secondary>
-  </indexterm>
-  <para>
-    From version 4, &repmgr; consists of three elements:
-     <itemizedlist spacing="compact" mark="bullet">
-
-       <listitem>
-         <simpara>
-           the <application>repmgr</application> and &repmgrd; executables
-         </simpara>
-       </listitem>
-
-       <listitem>
-         <simpara>
-           the objects for the &repmgr; PostgreSQL extension (SQL files for creating/updating
-           repmgr metadata, and the extension control file)
-         </simpara>
-       </listitem>
-
-       <listitem>
-         <simpara>
-           the shared library module used by &repmgrd; which
-           is resident in the PostgreSQL backend
-         </simpara>
-       </listitem>
-     </itemizedlist>
-  </para>
-  <para>
-    With <emphasis>minor releases</emphasis>, usually changes are only made to the <application>repmgr</application>
-    and &repmgrd; executables. In this case, the upgrade is quite straightforward,
-    and is simply a case of installing the new version, and restarting &repmgrd;
-    (if running).
-  </para>
-
-  <para>
-    For <emphasis>major releases</emphasis>, the &repmgr; PostgreSQL extension will need to be updated
-    to the latest version. Additionally, if the shared library module has been updated (this is sometimes,
-    but not always the case), PostgreSQL itself will need to be restarted on each node.
-  </para>
-  <important>
-    <para>
-      Always check the <link linkend="appendix-release-notes">release notes</link> for every
-      release as they may contain upgrade instructions particular to individual versions.
-    </para>
-  </important>
-
-  <sect2 id="upgrading-minor-version" xreflabel="Upgrading a minor version release">
-	<title>Upgrading a minor version release</title>
-
-	<indexterm>
-	  <primary>upgrading</primary>
-	  <secondary>minor release</secondary>
-	</indexterm>
-
-    <para>
-	  A minor release upgrade involves updating &repmgr; from one minor release to another
-	  minor release within the same major release (e.g. <literal>5.3.1</literal> to <literal>5.3.2</literal>).
-	  An upgrade between minor releases of differing major releases (e.g. <literal>5.2.1</literal> to <literal>5.3.2</literal>)
-	  is a <link linkend="upgrading-major-version">major upgrade</link>.
-    </para>
-    <para>
-      The process for installing minor version upgrades is quite straightforward:
-
-      <itemizedlist spacing="compact" mark="bullet">
-
-        <listitem>
-          <simpara>
-            install the new &repmgr; version
-          </simpara>
-        </listitem>
-
-        <listitem>
-          <simpara>
-            restart &repmgrd; on all nodes where it is running
-          </simpara>
-        </listitem>
-
-      </itemizedlist>
-
-    </para>
-
-    <note>
-	  <para>
-        Some packaging systems (e.g. <link linkend="packages-debian-ubuntu">Debian/Ubuntu</link>
-        may restart &repmgrd; as part of the package upgrade process.
-      </para>
-    </note>
-
-	<para>
-	  Minor version upgrades can be performed in any order on the nodes in the replication
-	  cluster.
-	</para>
-
-	<para>
-	  A PostgreSQL restart is usually <emphasis>not</emphasis> required for minor version upgrades
-	  within the same major version (e.g. <literal>5.3.1</literal> to <literal>5.3.2</literal>).
-	  Be sure to check the <link linkend="appendix-release-notes">release notes</link>.
-	</para>
-
-    <note>
-	  <para>
-		The same &repmgr; &quot;major version&quot; (e.g. <literal>5.3</literal>) must be
-		installed on all nodes in the replication cluster. While it's possible to have differing
-		&repmgr; &quot;minor versions&quot; (e.g. <literal>5.3.1</literal> and <literal>5.3.2</literal>)
-		on different nodes, we strongly recommend updating all nodes to the latest minor version.
-	  </para>
-    </note>
-
-  </sect2>
-
-  <sect2 id="upgrading-major-version" xreflabel="Upgrading a major version release">
-	<title>Upgrading a major version release</title>
-
-	<indexterm>
-	  <primary>upgrading</primary>
-	  <secondary>major release</secondary>
-	</indexterm>
-
-	<para>
-	  &quot;major version&quot; upgrades need to be planned more carefully, as they may include
-	  changes to the &repmgr; metadata (which need to be propagated from the primary to all
-	  standbys) and/or changes to the shared object file used by &repmgrd;
-	  (which require a PostgreSQL restart).
-	</para>
-	<para>
-	  With this in mind,
-	</para>
-
-	<para>
-      <orderedlist>
-
-		<listitem>
-          <simpara>
-			Stop &repmgrd; (if in use) on all nodes where it is running.
-          </simpara>
-		</listitem>
-
-		<listitem>
-          <simpara>
-			Disable the &repmgrd; service on all nodes where it is in use;
-            this is to prevent packages from prematurely restarting &repmgrd;.
-          </simpara>
-		</listitem>
-
-		<listitem>
-          <simpara>
-			Install the updated package (or compile the updated source) on all nodes.
-          </simpara>
-		</listitem>
-
-        <listitem>
-          <para>
-            If running a <literal>systemd</literal>-based Linux distribution, execute (as <literal>root</literal>,
-            or with appropriate <literal>sudo</literal> permissions):
-            <programlisting>
-systemctl daemon-reload</programlisting>
-          </para>
-        </listitem>
-
-		<listitem>
-          <simpara>
-			If the &repmgr; shared library module has been updated (check the <link linkend="appendix-release-notes">release notes</link>!),
-            restart PostgreSQL, then &repmgrd; (if in use)	on each node,
-            The order in which this is applied to individual nodes is not critical,
-			and it's also fine to restart PostgreSQL on all nodes first before starting &repmgrd;.
-		  </simpara>
-		  <simpara>
-			Note that if the upgrade requires a PostgreSQL restart, &repmgrd;
-			will only function correctly once all nodes have been restarted.
-          </simpara>
-		</listitem>
-
-		<listitem>
-          <para>
-			On the primary node, execute
-			<programlisting>
-ALTER EXTENSION repmgr UPDATE</programlisting>
-			in the database where &repmgr; is installed.
-          </para>
-		</listitem>
-
-		<listitem>
-          <simpara>
-			Reenable the &repmgrd; service on all nodes where it is in use, and
-            ensure it is running.
-          </simpara>
-		</listitem>
-
-	  </orderedlist>
-	</para>
-	<tip>
-	  <para>
-        If the &repmgr; upgrade requires a PostgreSQL restart, combine the &repmgr; upgrade
-        with a PostgreSQL minor version upgrade, which will require a restart in any case.
-      </para>
-      <para>
-		New PostgreSQL minor versions are usually released every couple of months;
-        see the <ulink url="https://www.postgresql.org/developer/roadmap/">Roadmap</ulink>
-        for the current schedule.
-	  </para>
-	</tip>
-  </sect2>
-
-  <sect2 id="upgrading-check-repmgrd" xreflabel="Checking repmgrd status after an upgrade">
-	<title>Checking repmgrd status after an upgrade</title>
-
-	<indexterm>
-	  <primary>upgrading</primary>
-	  <secondary>checking repmgrd status</secondary>
-	</indexterm>
-	<para>
-      From <link linkend="release-4.2">repmgr 4.2</link>, once the upgrade is complete, execute the
-      <command><link linkend="repmgr-service-status">repmgr service status</link></command>
-      (&repmgr; 4.2 - 4.4: <command><link linkend="repmgr-service-status">repmgr daemon status</link></command>)
-      command (on any node) to show an overview of the status of &repmgrd; on all nodes.
-    </para>
-  </sect2>
- </sect1>
-
- <sect1 id="upgrading-and-pg-upgrade" xreflabel="pg_upgrade and repmgr">
-  <title>pg_upgrade and repmgr</title>
-
-  <indexterm>
-   <primary>upgrading</primary>
-   <secondary>pg_upgrade</secondary>
-  </indexterm>
-  <indexterm>
-    <primary>pg_upgrade</primary>
-  </indexterm>
-
-  <para>
-    <application>pg_upgrade</application> requires that if any functions are
-    dependent on a shared library, this library must be present in both
-    the old and new installations before <application>pg_upgrade</application>
-    can be executed.
-  </para>
-  <para>
-    To minimize the risk of any upgrade issues (particularly if an upgrade to
-    a new major &repmgr; version is involved), we recommend upgrading
-    &repmgr; on the old server <emphasis>before</emphasis> running
-    <application>pg_upgrade</application> to ensure that old and new
-    versions are the same.
-  </para>
-  <note>
-    <simpara>
-      This issue applies to any PostgreSQL extension which has
-      dependencies on a shared library.
-    </simpara>
-  </note>
-  <para>
-    For further details please see the <ulink url="https://www.postgresql.org/docs/current/pgupgrade.html">pg_upgrade documentation</ulink>.
-  </para>
-  <para>
-    If replication slots are in use, bear in mind these will <emphasis>not</emphasis>
-    be recreated by <application>pg_upgrade</application>. These will need to
-    be recreated manually.
-  </para>
-  <tip>
-	<para>
-	  Use <command><link linkend="repmgr-node-check">repmgr node check</link></command>
-	  to determine which replication slots need to be recreated.
-	</para>
-  </tip>
-
-  <sect2 id="upgrading-pg-upgrade-standby" xreflabel="pg_upgrade and upgrading standbys">
-    <title>Upgrading standbys with pg_upgrade and rsync</title>
-    <para>
-      If you are intending to upgrade a standby using the <command>rsync</command> method described
-      in the <ulink url="https://www.postgresql.org/docs/current/pgupgrade.html#PGUPGRADE-STEP-REPLICAS">pg_upgrade documentation</ulink>,
-      you <emphasis>must</emphasis> ensure the standby's replication configuration is present and correct
-      before starting the standby.
-    </para>
-    <para>
-      Use <link linkend="repmgr-standby-clone">repmgr standby clone --replication-conf-only</link> to generate
-      the correct replication configuration.
-    </para>
-
-    <tip>
-	  <para>
-        If upgrading from PostgreSQL 11 or earlier, be sure to delete <filename>recovery.conf</filename>, if present,
-        otherwise PostgreSQL will refuse to start.
-      </para>
-    </tip>
-
-  </sect2>
-
-
- </sect1>
-
-
- <sect1 id="upgrading-from-repmgr-3" xreflabel="Upgrading from repmgr 3.x">
-  <title>Upgrading from repmgr 3.x</title>
-
-  <indexterm>
-   <primary>upgrading</primary>
-   <secondary>from repmgr 3.x</secondary>
-  </indexterm>
-
-  <para>
-   The upgrade process consists of two steps:
-   <orderedlist>
-    <listitem>
-     <simpara>
-       converting the <filename>repmgr.conf</filename> configuration files
-     </simpara>
-    </listitem>
-    <listitem>
-     <simpara>
-       upgrading the repmgr schema using <command>CREATE EXTENSION</command> (PostgreSQL 12 and earlier)
-     </simpara>
-    </listitem>
-   </orderedlist>
-  </para>
-  <para>
-   A script is provided to assist with converting <filename>repmgr.conf</filename>.
-  </para>
-  <para>
-   The schema upgrade (which converts the &repmgr; metadata into
-   a packaged PostgreSQL extension) is normally carried out
-   automatically when the &repmgr; extension is created.
-  </para>
-  <para>
-   The shared library has been renamed from <literal>repmgr_funcs</literal> to
-   <literal>repmgr</literal> - if it's set in <varname>shared_preload_libraries</varname>
-   in <filename>postgresql.conf</filename> it will need to be updated to the new name:
-   <programlisting>
-    shared_preload_libraries = 'repmgr'</programlisting>
-  </para>
-
-  <sect2 id="converting-repmgr-conf">
-   <title>Converting repmgr.conf configuration files</title>
-   <para>
-    With a completely new repmgr version, we've taken the opportunity
-    to rename some configuration items for
-    clarity and consistency, both between the configuration file and
-    the column names in <structname>repmgr.nodes</structname>
-    (e.g. <varname>node</varname> to <varname>node_id</varname>), and
-    also for consistency with PostgreSQL naming conventions
-    (e.g. <varname>loglevel</varname> to <varname>log_level</varname>).
-   </para>
-   <para>
-    Other configuration items have been changed to command line options,
-    and vice-versa, e.g. to avoid hard-coding items such as a a node's
-    upstream ID, which might change over time.
-   </para>
-   <para>
-    &repmgr; will issue a warning about deprecated/altered options.
-   </para>
-   <sect3>
-    <title>Changed parameters in "repmgr.conf"</title>
-    <para>
-     Following parameters have been added:
-     <itemizedlist spacing="compact" mark="bullet">
-      <listitem>
-        <simpara><varname>data_directory</varname>: this is mandatory and must
-         contain the path to the node's data directory</simpara>
-      </listitem>
-      <listitem>
-        <simpara><varname>monitoring_history</varname>: this replaces the
-          &repmgrd; command line option
-          <literal>--monitoring-history</literal></simpara>
-      </listitem>
-     </itemizedlist>
-    </para>
-    <para>
-     Following parameters have been renamed:
-    </para>
-    <table tocentry="1" id="repmgr3-repmgr4-renamed-parameters">
-     <title>Parameters renamed in repmgr4</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>repmgr3</entry>
-        <entry>repmgr4</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><varname>node</varname></entry>
-        <entry><varname>node_id</varname></entry>
-       </row>
-       <row>
-        <entry><varname>loglevel</varname></entry>
-        <entry><varname>log_level</varname></entry>
-       </row>
-       <row>
-        <entry><varname>logfacility</varname></entry>
-        <entry><varname>log_facility</varname></entry>
-       </row>
-       <row>
-        <entry><varname>logfile</varname></entry>
-        <entry><varname>log_file</varname></entry>
-       </row>
-       <row>
-        <entry><varname>barman_server</varname></entry>
-        <entry><varname>barman_host</varname></entry>
-       </row>
-       <row>
-        <entry><varname>master_reponse_timeout</varname></entry>
-        <entry><varname>async_query_timeout</varname></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-    <note>
-      <para>
-        From &repmgr; 4, <literal>barman_server</literal> refers
-        to the server configured in Barman (in &repmgr; 3, the deprecated
-        <literal>cluster</literal> parameter was used for this);
-        the physical Barman hostname is configured with
-        <literal>barman_host</literal> (see <xref linkend="cloning-from-barman-prerequisites"/>
-          for details).
-      </para>
-    </note>
-    <para>
-     Following parameters have been removed:
-     <itemizedlist spacing="compact" mark="bullet">
-      <listitem>
-        <simpara><varname>cluster</varname>: is no longer required and will
-        be ignored.</simpara>
-      </listitem>
-      <listitem>
-        <simpara><varname>upstream_node</varname>:  is replaced by the
-        command-line parameter <literal>--upstream-node-id</literal></simpara>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </sect3>
-   <sect3>
-    <title>Conversion script</title>
-    <para>
-     To assist with conversion of <filename>repmgr.conf</filename> files, a Perl script
-     is provided in <filename>contrib/convert-config.pl</filename>.
-     Use like this:
-     <programlisting>
-    $ ./convert-config.pl /etc/repmgr.conf
-    node_id=2
-    node_name='node2'
-    conninfo='host=node2 dbname=repmgr user=repmgr connect_timeout=2'
-    pg_ctl_options='-l /var/log/postgres/startup.log'
-    rsync_options='--exclude=postgresql.local.conf --archive'
-    log_level='INFO'
-    pg_basebackup_options='--no-slot'
-    data_directory=''</programlisting>
-    </para>
-    <para>
-      The converted file is printed to <literal>STDOUT</literal> and the original file is not
-      changed.
-    </para>
-    <para>
-      Please note that the the conversion script will add an empty
-      placeholder parameter for <varname>data_directory</varname>, which
-      is a required parameter from &repmgr; 4. This must be manually modified to contain
-      the correct data directory.
-    </para>
-   </sect3>
-  </sect2>
-  <sect2>
-   <title>Upgrading the repmgr schema (PostgreSQL 12 and earlier)</title>
-   <para>
-    Ensure &repmgrd; is not running, or any cron jobs which execute the
-    <command>repmgr</command> binary.
-   </para>
-   <para>
-    Install the latest &repmgr; package; any <literal>repmgr 3.x</literal> packages
-    should be uninstalled (if not automatically uninstalled already by your packaging system).
-   </para>
-   <sect3>
-    <title>Upgrading from repmgr 3.1.1 or earlier</title>
-    <tip>
-     <simpara>
-      If you don't care about any data from the existing &repmgr; installation,
-      (e.g. the contents of the <structname>events</structname> and <structname>monitoring</structname>
-      tables), the following steps can be skipped; proceed to <xref linkend="upgrade-reregister-nodes"/>.
-     </simpara>
-    </tip>
-
-    <para>
-     If your repmgr version is 3.1.1 or earlier, you will need to update
-     the schema to the latest version in the 3.x series (3.3.2) before
-     converting the installation to repmgr 4.
-    </para>
-    <para>
-      To do this, apply the following upgrade scripts as appropriate for
-      your current version:
-      <itemizedlist spacing="compact" mark="bullet">
-      <listitem>
-        <simpara>
-          <ulink url="https://raw.githubusercontent.com/EnterpriseDB/repmgr/REL3_3_STABLE/sql/repmgr3.0_repmgr3.1.sql">repmgr3.0_repmgr3.1.sql</ulink></simpara>
-      </listitem>
-      <listitem>
-        <simpara><ulink url="https://raw.githubusercontent.com/EnterpriseDB/repmgr/REL3_3_STABLE/sql/repmgr3.1.1_repmgr3.1.2.sql">repmgr3.1.1_repmgr3.1.2.sql</ulink></simpara>
-      </listitem>
-      </itemizedlist>
-    </para>
-    <para>
-      For more details see the
-      <ulink url="https://repmgr.org/release-notes-3.3.2.html#upgrading">repmgr 3 upgrade notes</ulink>.
-    </para>
-   </sect3>
-   <sect3>
-    <title>Manually create the repmgr extension</title>
-    <para>
-     In the database used by the existing &repmgr; installation, execute:
-     <programlisting>
-      CREATE EXTENSION repmgr FROM unpackaged</programlisting>
-    </para>
-
-    <para>
-     This will move and convert all objects from the existing schema
-     into the new, standard <literal>repmgr</literal> schema.
-    </para>
-    <note>
-      <simpara>There must be only one schema matching <literal>repmgr_%</literal> in the
-        database, otherwise this step may not work.
-      </simpara>
-    </note>
-   </sect3>
-  </sect2>
-
-  <sect2>
-   <title>Upgrading the repmgr schema (PostgreSQL 13 and later)</title>
-   <para>
-     Beginning with PostgreSQL 13, the <command>CREATE EXTENSION ... FROM unpackaged</command>
-     syntax is no longer available. In the unlikely event you have ended up with an
-     installation running PostgreSQL 13 or later and containing the legacy &repmgr;
-     schema, there is no convenient way of upgrading this; instead you'll just need
-     to re-register the nodes as detailed in <link linkend="upgrade-reregister-nodes">the following section</link>,
-     which will create the &repmgr; extension automatically.
-   </para>
-   <para>
-     Any historical data you wish to retain (e.g. the contents of the <structname>events</structname>
-     and <structname>monitoring</structname> tables) will need to be exported manually.
-   </para>
-  </sect2>
-  <sect2 id="upgrade-reregister-nodes">
-    <title>Re-register each node</title>
-    <para>
-     This is necessary to update the <literal>repmgr</literal> metadata with some additional items.
-    </para>
-    <para>
-     On the primary node, execute e.g.
-     <programlisting>
-      repmgr primary register -f /etc/repmgr.conf --force</programlisting>
-    </para>
-    <para>
-      If not already present (e.g. after executing <command>CREATE EXTENSION repmgr FROM unpackaged</command>),
-      the &repmgr; extension will be automatically created by <command>repmgr primary register</command>.
-    </para>
-    <para>
-     On each standby node, execute e.g.
-     <programlisting>
-      repmgr standby register -f /etc/repmgr.conf --force</programlisting>
-    </para>
-    <para>
-     Check the data is updated as expected by examining the <structname>repmgr.nodes</structname>
-     table; restart &repmgrd; if required.
-    </para>
-    <para>
-     The original <literal>repmgr_$cluster</literal> schema can be dropped at any time.
-    </para>
-
-  </sect2>
-
-  <sect2 id="upgrade-drop-repmgr-cluster-schema">
-    <title>Drop the legacy repmgr schema</title>
-    <para>
-      Once the cluster has been registered with the current &repmgr; version, the legacy
-      <literal>repmgr_$cluster</literal> schema can be dropped at any time with:
-<programlisting>
-    DROP SCHEMA repmgr_$cluster CASCADE</programlisting>
-      (substitute <literal>$cluster</literal> with the value of the <varname>clustername</varname>
-      variable used in &repmgr; 3.x).
-    </para>
-  </sect2>
- </sect1>
-
-</chapter>

doc/website-docs.css

@@ -1,534 +0,0 @@
-/* PostgreSQL.org Documentation Style */
-
-/*
- * Documentation generated by XSL stylesheets has lower-case class
- * names, older documentation generated by DSSSL stylesheets has
- * upper-case class names, so we need to support both for a while.  In
- * some cases, the elements and classes differ further between the two
- * stylesheets.
- */
-
-/* requires global.css, table.css and text.css to be loaded before this file! */
-body {
-  font-size: 76%;
-}
-
-.navheader table,
-.NAVHEADER table {
-  margin-left: 0;
-}
-
-/* Container Definitions */
-
-#docContainerWrap {
-  text-align: center; /* Win IE5 */
-}
-
-#docContainer {
-  margin: 0 auto;
-  width: 90%;
-  padding-bottom: 2em;
-  display: block;
-  text-align: left; /* Win IE5 */
-}
-
-#docHeader {
-  background-image: url("/media/img/docs/bg_hdr.png");
-  height: 83px;
-  margin: 0px;
-  padding: 0px;
-  display: block;
-}
-
-#docHeaderLogo {
-  position: relative;
-  width: 206px;
-  height: 83px;
-  border: 0px;
-  padding: 0px;
-  margin: 0 0 0 20px;
-}
-
-#docHeaderLogo img {
-  border: 0px;
-}
-
-#docNavSearchContainer {
-  padding-bottom: 2px;
-}
-
-#docNav, #docVersions {
-  position: relative;
-  text-align: left;
-  margin-left: 10px;
-  margin-top: 5px;
-  color: #666;
-  font-size: 0.95em;
-}
-
-#docSearch {
-  position: relative;
-  text-align: right;
-  padding: 0;
-  margin: 0;
-  color: #666;
-}
-
-#docTextSize {
-  text-align: right;
-  white-space: nowrap;
-  margin-top: 7px;
-  font-size: 0.95em;
-}
-
-#docSearch form {
-  position: relative;
-  top: 5px;
-  right: 0;
-  margin: 0; /* need for IE 5.5 OSX */
-  text-align: right; /* need for IE 5.5 OSX */
-  white-space: nowrap; /* for Opera */
-}
-
-#docSearch form label {
-  color: #666;
-  font-size: 0.95em;
-}
-
-#docSearch form input {
-  font-size: 0.95em;
-}
-
-#docSearch form #submit {
-  font-size: 0.95em;
-  background: #7A7A7A;
-  color: #fff;
-  border: 1px solid #7A7A7A;
-  padding: 1px 4px;
-}
-
-#docSearch form #q {
-  width: 170px;
-  font-size: 0.95em;
-  border:  1px solid #7A7A7A;
-  background: #E1E1E1;
-  color: #000000;
-  padding: 2px;
-}
-
-.frmDocSearch {
-  padding: 0;
-  margin: 0;
-  display: inline;
-}
-
-.inpDocSearch {
-  padding: 0;
-  margin: 0;
-  color: #000;
-}
-
-#docContent {
-  position: relative;
-  margin-left: 10px;
-  margin-right: 10px;
-  margin-top: 40px;
-}
-
-#docFooter {
-  position: relative;
-  font-size: 0.9em;
-  color: #666;
-  line-height: 1.3em;
-  margin-left: 10px;
-  margin-right: 10px;
-}
-
-#docComments {
-  margin-top: 10px;
-}
-
-#docClear {
-  clear: both;
-  margin: 0;
-  padding: 0;
-}
-
-/* Heading Definitions */
-
-h1, h2, h3 {
-  font-weight: bold;
-  margin-top: 2ex;
-}
-
-h1 {
-  font-size: 1.4em;
-}
-
-h2 {
-  font-size: 1.2em !important;
-}
-
-h3 {
-  font-size: 1.1em;
-}
-
-h1 a:hover {
-  color: #EC5800;
-  text-decoration: none;
-}
-
-h2 a:hover,
-h3 a:hover,
-h4 a:hover {
-  color: #666666;
-  text-decoration: none;
-}
-
-/*
- * Change color of h2 chunk titles in XSL build.  (In DSSSL build,
- * these will be h1, which is already handled elsewhere.)
- */
-.titlepage h2.title,
-.refnamediv h2 {
-  color: #EC5800;
-}
-
-/* Text Styles */
-
-div.sect2,
-div.SECT2 {
-  margin-top: 4ex;
-}
-
-div.sect3,
-div.SECT3 {
-  margin-top: 3ex;
-  margin-left: 3ex;
-}
-
-.txtCurrentLocation {
-  font-weight: bold;
-}
-
-p, ol, ul, li {
-  line-height: 1.5em;
-}
-
-.txtCommentsWrap {
-  border: 2px solid #F5F5F5;
-  width: 100%;
-}
-
-.txtCommentsContent {
-  background: #F5F5F5;
-  padding: 3px;
-}
-
-.txtCommentsPoster {
-  float: left;
-}
-
-.txtCommentsDate {
-  float: right;
-}
-
-.txtCommentsComment {
-  padding: 3px;
-}
-
-#docContainer pre code,
-#docContainer pre tt,
-#docContainer pre pre,
-#docContainer tt tt,
-#docContainer tt code,
-#docContainer tt pre {
-  font-size: 1em;
-}
-
-pre.literallayout,
-.screen,
-.synopsis,
-.programlisting,
-.refsynopsisdiv p,
-.caution,
-.warning,
-.note,
-.tip,
-.table table,
-.informaltable table,
-pre.LITERALLAYOUT,
-.SCREEN,
-.SYNOPSIS,
-.PROGRAMLISTING,
-.REFSYNOPSISDIV p,
-table.CAUTION,
-table.WARNING,
-blockquote.NOTE,
-blockquote.TIP,
-table.CALSTABLE {
-  -moz-box-shadow: 3px 3px 5px #DFDFDF;
-  -webkit-box-shadow: 3px 3px 5px #DFDFDF;
-  -khtml-box-shadow: 3px 3px 5px #DFDFDF;
-  -o-box-shadow: 3px 3px 5px #DFDFDF;
-  box-shadow: 3px 3px 5px #DFDFDF;
-}
-
-pre.literallayout,
-.screen,
-.synopsis,
-.programlisting,
-.refsynopsisdiv p,
-.caution,
-.warning,
-.note,
-.tip,
-pre.LITERALLAYOUT,
-.SCREEN,
-.SYNOPSIS,
-.PROGRAMLISTING,
-.REFSYNOPSISDIV p,
-table.CAUTION,
-table.WARNING,
-blockquote.NOTE,
-blockquote.TIP {
-  color: black;
-  border-width: 1px;
-  border-style: solid;
-  padding: 2ex;
-  margin: 2ex 0 2ex 2ex;
-  overflow: auto;
-  -moz-border-radius: 8px;
-  -webkit-border-radius: 8px;
-  -khtml-border-radius: 8px;
-  border-radius: 8px;
-}
-
-pre.literallayout,
-pre.synopsis,
-pre.programlisting,
-.refsynopsisdiv p,
-.screen,
-pre.LITERALLAYOUT,
-pre.SYNOPSIS,
-pre.PROGRAMLISTING,
-.REFSYNOPSISDIV p,
-.SCREEN {
-  border-color: #CFCFCF;
-  background-color: #F7F7F7;
-}
-
-.note,
-.tip,
-blockquote.NOTE,
-blockquote.TIP {
-  border-color: #DBDBCC;
-  background-color: #EEEEDD;
-  padding: 14px;
-  width: 572px;
-}
-
-.note,
-.tip,
-.caution,
-.warning,
-blockquote.NOTE,
-blockquote.TIP,
-table.CAUTION,
-table.WARNING {
-  margin: 4ex auto;
-}
-
-.note p,
-.tip p,
-blockquote.NOTE p,
-blockquote.TIP p {
-  margin: 0;
-}
-
-.note pre,
-.note code,
-.tip pre,
-.tip code,
-blockquote.NOTE pre,
-blockquote.NOTE code,
-blockquote.TIP pre,
-blockquote.TIP code {
-  margin-left: 0;
-  margin-right: 0;
-  -moz-box-shadow: none;
-  -webkit-box-shadow: none;
-  -khtml-box-shadow: none;
-  -o-box-shadow: none;
-  box-shadow: none;
-}
-
-.caution,
-.warning {
-  max-width: 600px;
-}
-
-.tip h3,
-.note h3,
-.caution h3,
-.warning h3 {
-  text-align: center;
-}
-
-.emphasis,
-.c2 {
-  font-weight: bold;
-}
-
-.replaceable,
-.REPLACEABLE {
-  font-style: italic;
-}
-
-/* Table Styles */
-
-table {
-  margin-left: 2ex;
-}
-
-.table table td,
-.table table th,
-.informaltable table td,
-.informaltable table th,
-table.CALSTABLE td,
-table.CALSTABLE th,
-table.CAUTION td,
-table.CAUTION th,
-table.WARNING td,
-table.WARNING th {
-  border-style: solid;
-}
-
-.table table,
-.informaltable table,
-table.CALSTABLE,
-table.CAUTION,
-table.WARNING {
-  border-spacing: 0;
-  border-collapse: collapse;
-}
-
-.table table,
-.informaltable table,
-table.CALSTABLE
-{
-  margin: 2ex 0 2ex 2ex;
-  background-color: #E0ECEF;
-  border: 2px solid #A7C6DF;
-}
-
-.table table tr:hover td,
-.informaltable table tr:hover td,
-table.CALSTABLE tr:hover td
-{
-  background-color: #EFEFEF;
-}
-
-.table table td,
-.informaltable table td,
-table.CALSTABLE td {
-  background-color: #FFF;
-}
-
-.table table td,
-.table table th,
-.informaltable table td,
-.informaltable table th,
-table.CALSTABLE td,
-table.CALSTABLE th {
-  border: 1px solid #A7C6DF;
-  padding: 0.5ex 0.5ex;
-}
-
-table.CAUTION,
-table.WARNING {
-  border-collapse: separate;
-  display: block;
-  padding: 0;
-  max-width: 600px;
-}
-
-.caution,
-table.CAUTION {
-  background-color: #F5F5DC;
-  border-color: #DEDFA7;
-}
-
-.warning,
-table.WARNING {
-  background-color: #FFD7D7;
-  border-color: #DF421E;
-}
-
-table.CAUTION td,
-table.CAUTION th,
-table.WARNING td,
-table.WARNING th {
-  border-width: 0;
-  padding-left: 2ex;
-  padding-right: 2ex;
-}
-
-table.CAUTION td,
-table.CAUTION th {
-  border-color: #F3E4D5
-}
-
-table.WARNING td,
-table.WARNING th {
-  border-color: #FFD7D7;
-}
-
-td.c1,
-td.c2,
-td.c3,
-td.c4,
-td.c5,
-td.c6 {
-  font-size: 1.1em;
-  font-weight: bold;
-  border-bottom: 0px solid #FFEFEF;
-  padding: 1ex 2ex 0;
-}
-
-/* Link Styles */
-
-#docNav a {
-  font-weight: bold;
-}
-
-a:link,
-a:visited,
-a:active,
-a:hover {
-  text-decoration: underline;
-}
-
-a:link,
-a:active {
-  color:#0066A2;
-}
-
-a:visited {
-  color:#004E66;
-}
-
-a:hover {
-  color:#000000;
-}
-
-#docFooter a:link,
-#docFooter a:visited,
-#docFooter a:active {
-  color:#666;
-}
-
-#docContainer code.function tt,
-#docContainer code.FUNCTION tt {
-  font-size: 1em;
-}

errcode.h

@@ -1,6 +1,6 @@
 /*
  * errcode.h
- * Copyright (c) EnterpriseDB Corporation, 2010-2021
+ * Copyright (c) 2ndQuadrant, 2010-2017
  *
  * This program is free software: you can redistribute it and/or modify
  * it under the terms of the GNU General Public License as published by
@@ -43,12 +43,5 @@
 #define ERR_BARMAN 19
 #define ERR_REGISTRATION_SYNC 20
 #define ERR_OUT_OF_MEMORY 21
-#define ERR_SWITCHOVER_INCOMPLETE 22
-#define ERR_FOLLOW_FAIL 23
-#define ERR_REJOIN_FAIL 24
-#define ERR_NODE_STATUS 25
-#define ERR_REPMGRD_PAUSE 26
-#define ERR_REPMGRD_SERVICE 27
-#define ERR_PGBACKUPAPI_SERVICE 28
 
 #endif							/* _ERRCODE_H_ */

expected/repmgr_extension.out

@@ -32,10 +32,22 @@ SELECT * FROM repmgr.show_nodes;
 (0 rows)
 
 -- functions
+SELECT repmgr.am_bdr_failover_handler(-1);
+ am_bdr_failover_handler 
+-------------------------
+ 
+(1 row)
+
 SELECT repmgr.get_new_primary();
  get_new_primary 
 -----------------
-              -1
+                
+(1 row)
+
+SELECT repmgr.get_voting_status();
+ get_voting_status 
+-------------------
+                  
 (1 row)
 
 SELECT repmgr.notify_follow_primary(-1);
@@ -44,9 +56,15 @@ SELECT repmgr.notify_follow_primary(-1);
  
 (1 row)
 
-SELECT repmgr.notify_follow_primary(NULL);
+SELECT repmgr.other_node_is_candidate(-1,-1);
- notify_follow_primary 
+ other_node_is_candidate 
------------------------
+-------------------------
+ 
+(1 row)
+
+SELECT repmgr.request_vote(-1,-1);
+ request_vote 
+--------------
  
 (1 row)
 
@@ -62,9 +80,9 @@ SELECT repmgr.set_local_node_id(-1);
  
 (1 row)
 
-SELECT repmgr.set_local_node_id(NULL);
+SELECT repmgr.set_voting_status_initiated();
- set_local_node_id 
+ set_voting_status_initiated 
--------------------
+-----------------------------
                             
 (1 row)
 
@@ -80,3 +98,9 @@ SELECT repmgr.standby_set_last_updated();
  
 (1 row)
 
+SELECT repmgr.unset_bdr_failover_handler();
+ unset_bdr_failover_handler 
+----------------------------
+ 
+(1 row)
+