diff --git a/.gitignore b/.gitignore index 18c011e8..2791c583 100644 --- a/.gitignore +++ b/.gitignore @@ -42,8 +42,6 @@ lib*.pc /regression.diffs /regression.out -/doc/Makefile - # other /.lineno *.dSYM diff --git a/Makefile.in b/Makefile.in index 4dbe8808..ad6cc229 100644 --- a/Makefile.in +++ b/Makefile.in @@ -77,12 +77,6 @@ Makefile: Makefile.in config.status configure Makefile.global: Makefile.global.in config.status configure ./config.status $@ -doc: - $(MAKE) -C doc all - -install-doc: - $(MAKE) -C doc install - clean: additional-clean maintainer-clean: additional-maintainer-clean @@ -91,7 +85,6 @@ additional-clean: rm -f *.o additional-maintainer-clean: clean - $(MAKE) -C doc maintainer-clean rm -f config.status config.log rm -f config.h rm -f repmgr_version.h diff --git a/configure b/configure index f066c3a8..b67639cb 100755 --- a/configure +++ b/configure @@ -1,6 +1,6 @@ #! /bin/sh # Guess values for system-dependent variables and create Makefiles. -# Generated by GNU Autoconf 2.69 for repmgr 4.3. +# Generated by GNU Autoconf 2.69 for repmgr 4.4. # # Report bugs to . # @@ -582,8 +582,8 @@ MAKEFLAGS= # Identity of this package. PACKAGE_NAME='repmgr' PACKAGE_TARNAME='repmgr' -PACKAGE_VERSION='4.3' -PACKAGE_STRING='repmgr 4.3' +PACKAGE_VERSION='4.4' +PACKAGE_STRING='repmgr 4.4' PACKAGE_BUGREPORT='repmgr@googlegroups.com' PACKAGE_URL='https://repmgr.org/' @@ -1178,7 +1178,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 4.3 to adapt to many kinds of systems. +\`configure' configures repmgr 4.4 to adapt to many kinds of systems. Usage: $0 [OPTION]... [VAR=VALUE]... @@ -1239,7 +1239,7 @@ fi if test -n "$ac_init_help"; then case $ac_init_help in - short | recursive ) echo "Configuration of repmgr 4.3:";; + short | recursive ) echo "Configuration of repmgr 4.4:";; esac cat <<\_ACEOF @@ -1313,7 +1313,7 @@ fi test -n "$ac_init_help" && exit $ac_status if $ac_init_version; then cat <<\_ACEOF -repmgr configure 4.3 +repmgr configure 4.4 generated by GNU Autoconf 2.69 Copyright (C) 2012 Free Software Foundation, Inc. @@ -1332,7 +1332,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 4.3, which was +It was created by repmgr $as_me 4.4, which was generated by GNU Autoconf 2.69. Invocation command line was $ $0 $@ @@ -1851,8 +1851,6 @@ ac_config_files="$ac_config_files Makefile" ac_config_files="$ac_config_files Makefile.global" -ac_config_files="$ac_config_files doc/Makefile" - cat >confcache <<\_ACEOF # This file is a shell script that caches the results of configure # tests run on this system so they can be shared between configure @@ -2359,7 +2357,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 4.3, which was +This file was extended by repmgr $as_me 4.4, which was generated by GNU Autoconf 2.69. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -2422,7 +2420,7 @@ _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 4.3 +repmgr config.status 4.4 configured by $0, generated by GNU Autoconf 2.69, with options \\"\$ac_cs_config\\" @@ -2546,7 +2544,6 @@ do "config.h") CONFIG_HEADERS="$CONFIG_HEADERS config.h" ;; "Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;; "Makefile.global") CONFIG_FILES="$CONFIG_FILES Makefile.global" ;; - "doc/Makefile") CONFIG_FILES="$CONFIG_FILES doc/Makefile" ;; *) as_fn_error $? "invalid argument: \`$ac_config_target'" "$LINENO" 5;; esac diff --git a/configure.in b/configure.in index 8bc90ecd..a06368ac 100644 --- a/configure.in +++ b/configure.in @@ -59,6 +59,5 @@ AC_SUBST(vpath_build) AC_CONFIG_FILES([Makefile]) AC_CONFIG_FILES([Makefile.global]) -AC_CONFIG_FILES([doc/Makefile]) AC_OUTPUT diff --git a/doc/Makefile b/doc/Makefile new file mode 100644 index 00000000..05574afa --- /dev/null +++ b/doc/Makefile @@ -0,0 +1,61 @@ +# 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 + +override XSLTPROCFLAGS += --stringparam repmgr.version '$(REPMGR_VERSION)' + +ALLSGML := $(wildcard $(srcdir)/*.sgml) +GENERATED_SGML = version.sgml + +## +## HTML +## + + +html: html-stamp + +html-stamp: stylesheet.xsl repmgr.sgml $(ALLSGML) $(GENERATED_SGML) + $(XMLLINT) $(XMLINCLUDE) --noout --valid $(word 2,$^) + $(XSLTPROC) $(XMLINCLUDE) $(XSLTPROCFLAGS) $(XSLTPROC_HTML_FLAGS) $(wordlist 1,2,$^) + cp $(srcdir)/stylesheet.css html/ + touch $@ + +version.sgml: $(repmgr_top_builddir)/repmgr_version.h + { \ + echo ""; \ + } > $@ + +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) + +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_SGML) + +maintainer-clean: + rm -rf html + +.PHONY: html diff --git a/doc/Makefile.in b/doc/Makefile.in deleted file mode 100644 index 6fbd8de7..00000000 --- a/doc/Makefile.in +++ /dev/null @@ -1,76 +0,0 @@ -repmgr_subdir = doc -repmgr_top_builddir = .. -include $(repmgr_top_builddir)/Makefile.global - -ifndef JADE -JADE = $(missing) jade -endif - -SGMLINCLUDE = -D . -D ${srcdir} - -SPFLAGS += -wall -wno-unused-param -wno-empty -wfully-tagged - -JADE.html.call = $(JADE) $(JADEFLAGS) $(SPFLAGS) $(SGMLINCLUDE) $(CATALOG) -t sgml -i output-html - -ALLSGML := $(wildcard $(srcdir)/*.sgml) -# to build bookindex -ALMOSTALLSGML := $(filter-out %bookindex.sgml,$(ALLSGML)) -GENERATED_SGML = version.sgml bookindex.sgml - -Makefile: Makefile.in - cd $(repmgr_top_builddir) && ./config.status doc/Makefile - -all: html - -html: html-stamp - -html-stamp: repmgr.sgml $(ALLSGML) $(GENERATED_SGML) stylesheet.dsl website-docs.css - $(MKDIR_P) html - $(JADE.html.call) -d stylesheet.dsl -i include-index $< - cp $(srcdir)/stylesheet.css $(srcdir)/website-docs.css html/ - touch $@ - -repmgr.html: repmgr.sgml $(ALLSGML) $(GENERATED_SGML) stylesheet.dsl website-docs.css - sed '/html-index-filename/a\ -(define nochunks #t)' nochunks.dsl - $(JADE.html.call) -d nochunks.dsl -i include-index $< >repmgr.html - -version.sgml: ${repmgr_top_builddir}/repmgr_version.h - { \ - echo ""; \ - } > $@ - -HTML.index: repmgr.sgml $(ALMOSTALLSGML) stylesheet.dsl - @$(MKDIR_P) html - $(JADE.html.call) -d stylesheet.dsl -V html-index $< - -website-docs.css: - @$(MKDIR_P) html - curl http://www.postgresql.org/media/css/docs.css > ${srcdir}/website-docs.css - -bookindex.sgml: HTML.index -ifdef COLLATEINDEX - LC_ALL=C $(PERL) $(COLLATEINDEX) -f -g -i 'bookindex' -o $@ $< -else - @$(missing) collateindex.pl $< $@ -endif - -clean: - rm -f html-stamp - rm -f HTML.index $(GENERATED_SGML) - -maintainer-clean: - rm -rf html - rm -f Makefile - -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) - -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 - -.PHONY: html all diff --git a/doc/appendix-faq.sgml b/doc/appendix-faq.sgml index 796349ac..e95ceaba 100644 --- a/doc/appendix-faq.sgml +++ b/doc/appendix-faq.sgml @@ -1,9 +1,10 @@ - - FAQ (Frequently Asked Questions) - - FAQ (Frequently Asked Questions) + FAQ (Frequently Asked Questions) + + + FAQ (Frequently Asked Questions) + General @@ -125,7 +126,7 @@ How can I obtain old versions of &repmgr; packages? - See appendix for details. + See appendix for details. @@ -251,8 +252,8 @@ &repmgr; provides the command repmgr node rejoin which can - optionally execute pg_rewind; see the - documentation for details, in particular the section . + optionally execute pg_rewind; see the + documentation for details, in particular the section . If pg_rewind cannot be used, then the data directory will need @@ -276,7 +277,7 @@ directory in /etc? Use the command line option --copy-external-config-files. For more details - see . + see . @@ -317,7 +318,7 @@ Provide the option --waldir (--xlogdir in PostgreSQL 9.6 and earlier) with the absolute path to the WAL directory in pg_basebackup_options. - For more details see . + For more details see . @@ -387,7 +388,7 @@ How can I get &repmgrd; to rotate its logfile? - Configure your system's logrotate service to do this; see . + Configure your system's logrotate service to do this; see . @@ -410,7 +411,7 @@ promote_command or follow_command can be user-defined scripts, so &repmgr; will not apply even if excuting &repmgr;. Always provide the full - path; see for more details. + path; see for more details. diff --git a/doc/appendix-packages.sgml b/doc/appendix-packages.sgml index c49c6a36..f0d6336c 100644 --- a/doc/appendix-packages.sgml +++ b/doc/appendix-packages.sgml @@ -1,9 +1,11 @@ + + &repmgr; package details + packages - &repmgr; package details This section provides technical details about various &repmgr; binary packages, such as location of the installed binaries and @@ -309,7 +311,7 @@ version number for your installation. - See also for some specifics related + See also for some specifics related to configuring the &repmgrd; daemon. @@ -508,7 +510,7 @@ repmgr96-4.1.1-0.0git320.g5113ab0.1.el7.x86_64.rpm Old versions can be located with e.g.: yum --showduplicates list repmgr96 - (substitute the appropriate package name; see ) and installed with: + (substitute the appropriate package name; see ) and installed with: yum install {package_name}-{version} where {package_name} is the base package name (e.g. repmgr96) @@ -546,7 +548,7 @@ repmgr96-4.1.1-0.0git320.g5113ab0.1.el7.x86_64.rpm char package_conf_file[MAXPGPATH] = ""; - See also: + See also: @@ -560,7 +562,7 @@ repmgr96-4.1.1-0.0git320.g5113ab0.1.el7.x86_64.rpm char package_pid_file[MAXPGPATH] = ""; - See also: + See also: diff --git a/doc/appendix-release-notes.sgml b/doc/appendix-release-notes.sgml index 3fd15433..23ab922e 100644 --- a/doc/appendix-release-notes.sgml +++ b/doc/appendix-release-notes.sgml @@ -13,7 +13,7 @@ - See also: + See also: @@ -627,7 +627,7 @@ REPMGRD_OPTS="--daemonize=false" We recommend upgrading to this version as soon as possible. This release can be installed as a simple package upgrade from repmgr 4.0 ~ 4.1.0; &repmgrd; (if running) should be restarted. - See for more details. + See for more details. @@ -802,7 +802,7 @@ REPMGRD_OPTS="--daemonize=false" for this release (unless upgrading from repmgr 3.x). - See for more details. + See for more details. @@ -817,7 +817,7 @@ REPMGRD_OPTS="--daemonize=false" Coinciding with this release, the 2ndQuadrant repository structure has changed. - See section for details, particularly + See section for details, particularly if you are using a RPM-based system. @@ -830,7 +830,7 @@ REPMGRD_OPTS="--daemonize=false" - Default for is now . + Default for is now . This produces additional informative log output, without creating excessive additional log file volume, and matches the setting assumed for examples in the documentation. (GitHub #470). @@ -915,7 +915,7 @@ REPMGRD_OPTS="--daemonize=false" &repmgrd;: create a PID file by default - (GitHub #457). For details, see . + (GitHub #457). For details, see . @@ -990,7 +990,7 @@ REPMGRD_OPTS="--daemonize=false" We recommend upgrading to this version as soon as possible. This release can be installed as a simple package upgrade from repmgr 4.0 ~ 4.0.5; - &repmgrd; (if running) should be restarted. See + &repmgrd; (if running) should be restarted. See for more details. @@ -1126,7 +1126,7 @@ REPMGRD_OPTS="--daemonize=false" Add sanity check if not supplied when executing - (GitHub #395). + (GitHub #395). @@ -1252,7 +1252,7 @@ REPMGRD_OPTS="--daemonize=false" This release can be installed as a simple package upgrade from repmgr 4.0 ~ 4.0.3; - &repmgrd; (if running) should be restarted. See + &repmgrd; (if running) should be restarted. See for more details. @@ -1639,14 +1639,14 @@ REPMGRD_OPTS="--daemonize=false" - Fix when repmgr schema not set in search path + Fix when repmgr schema not set in search path (GitHub #341) - When using --force-rewind with + When using --force-rewind with delete any replication slots copied by pg_rewind (GitHub #334) @@ -1702,7 +1702,7 @@ REPMGRD_OPTS="--daemonize=false" - For detailed instructions on upgrading from repmgr 3.x, see . + For detailed instructions on upgrading from repmgr 3.x, see . @@ -1716,7 +1716,7 @@ REPMGRD_OPTS="--daemonize=false" the switchover process has been improved and streamlined, speeding up the switchover process and can also instruct other standbys to follow the new primary once the switchover has completed. See - for more details. + for more details. @@ -1767,8 +1767,8 @@ REPMGRD_OPTS="--daemonize=false" monitoring and status checks: - New commands and - providing information + New commands and + providing information about a node's status and replication-related monitoring output. @@ -1778,7 +1778,7 @@ REPMGRD_OPTS="--daemonize=false" node rejoin: - New commands enables a failed + New commands enables a failed primary to be rejoined to a replication cluster, optionally using pg_rewind to synchronise its data, (note that pg_rewind may not be useable @@ -1796,7 +1796,7 @@ REPMGRD_OPTS="--daemonize=false" functioning even if the monitored PostgreSQL instance is down, and resume monitoring if it reappears. Additionally, if the instance's role has changed (typically from a primary to a standby, e.g. following reintegration of a - failed primary using ) &repmgrd; + failed primary using ) &repmgrd; will automatically resume monitoring it as a standby. @@ -1860,7 +1860,7 @@ REPMGRD_OPTS="--daemonize=false" by the configuration file option replication_user. The value (which defaults to the user provided in the conninfo string) will be stored in the &repmgr; metadata for use by - and . + and . @@ -1875,7 +1875,7 @@ REPMGRD_OPTS="--daemonize=false" to primary_conninfo by default; to force the inclusion of a password (not recommended), use the new configuration file parameter use_primary_conninfo_password. For details, ee section - . + . diff --git a/doc/appendix-support.sgml b/doc/appendix-support.sgml index a4dcd3a7..c422a116 100644 --- a/doc/appendix-support.sgml +++ b/doc/appendix-support.sgml @@ -1,9 +1,11 @@ + + &repmgr; support + support - &repmgr; support 2ndQuadrant provides 24x7 production support for &repmgr; and other PostgreSQL @@ -28,12 +30,13 @@ + Reporting Issues + support reporting issues - Reporting Issues When asking questions or reporting issues, it is extremely helpful if the following information is included: @@ -48,7 +51,7 @@ - How was &repmgr installed? From source? From packages? If + How was &repmgr; installed? From source? From packages? If so from which repository? diff --git a/doc/cloning-standbys.sgml b/doc/cloning-standbys.sgml index da6e28ee..5ffccccd 100644 --- a/doc/cloning-standbys.sgml +++ b/doc/cloning-standbys.sgml @@ -2,6 +2,8 @@ Cloning standbys + Cloning a standby from Barman + cloning from Barman @@ -11,9 +13,8 @@ cloning a standby - Cloning a standby from Barman - can use + can use 2ndQuadrant's Barman application to clone a standby (and also as a fallback source for WAL files). @@ -73,7 +74,7 @@ the restore_command setting in repmgr.conf is configured to use a copy of the barman-wal-restore script shipped with the - barman-cli package (see section + barman-cli package (see section below). @@ -126,12 +127,13 @@ - + Using Barman as a WAL file source + + Barman fetching archived WAL - Using Barman as a WAL file source 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 @@ -172,7 +174,9 @@ - + + Cloning and replication slots + cloning replication slots @@ -182,7 +186,6 @@ replication slots cloning - Cloning and replication slots 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 @@ -244,18 +247,20 @@ As an alternative we recommend using 2ndQuadrant's Barman, 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 + slot for each individual standby to reserve WAL. See section for more details on using &repmgr; together with Barman. + Cloning and cascading replication + cloning cascading replication - Cloning and cascading replication + Cascading replication, introduced with PostgreSQL 9.2, enables a standby server to replicate from another standby server rather than directly from the primary, @@ -276,7 +281,7 @@ To demonstrate cascading replication, first ensure you have a primary and standby - set up as shown in the . + set up as shown in the . Then create an additional standby server with repmgr.conf looking like this: @@ -339,11 +344,11 @@ + Advanced cloning options cloning advanced options - Advanced cloning options pg_basebackup options when cloning a standby @@ -365,7 +370,7 @@ If Barman 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 . + is being cloned from. For more details see . @@ -433,7 +438,7 @@ (but not ~/.pgpass) and place it into the primary_conninfo string in recovery.conf. Note that PGPASSWORD will need to be set during any action which causes recovery.conf to be - rewritten, e.g. . + rewritten, e.g. . It is of course also possible to include the password value in the conninfo @@ -460,7 +465,7 @@ replication connections and generating recovery.conf. This value will also be stored in the parameter repmgr.nodes table for each node; it no longer needs to be explicitly specified when - cloning a node or executing . + cloning a node or executing . diff --git a/doc/configuration-file-log-settings.sgml b/doc/configuration-file-log-settings.sgml index e910b114..23cc6f59 100644 --- a/doc/configuration-file-log-settings.sgml +++ b/doc/configuration-file-log-settings.sgml @@ -1,4 +1,6 @@ + Log settings + repmgr.conf log settings @@ -7,7 +9,6 @@ log settings configuration in repmgr.conf - Log settings By default, &repmgr; and &repmgrd; write log output to @@ -32,12 +33,11 @@ - log_level (string) + log_level (string) + log_level configuration file parameter - - One of , , , , , , @@ -76,11 +76,11 @@ - If is set to , log output + If is set to , log output can be redirected to the specified file. - See for information on configuring log rotation. + See for information on configuring log rotation. diff --git a/doc/configuration-file-required-settings.sgml b/doc/configuration-file-required-settings.sgml index 62cf51c7..5f241f68 100644 --- a/doc/configuration-file-required-settings.sgml +++ b/doc/configuration-file-required-settings.sgml @@ -1,10 +1,12 @@ + + Required configuration file settings + repmgr.conf required settings - Required configuration file settings Each repmgr.conf file must contain the following parameters: @@ -60,7 +62,7 @@ For details on conninfo strings, see section Connection Strings + url="https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING">Connection Strings in the PosgreSQL documentation. @@ -69,18 +71,18 @@ string to determine the length of time which elapses before a network connection attempt is abandoned; for details see - the PostgreSQL documentation. + the PostgreSQL documentation. - data_directory (string) - - data_directory configuration file parameter - - + data_directory (string) + + data_directory configuration file parameter + + The node's data directory. This is needed by repmgr when performing operations when the PostgreSQL instance @@ -99,7 +101,7 @@ repmgr.conf.sample. - For &repmgrd;-specific settings, see . + For &repmgrd;-specific settings, see . diff --git a/doc/configuration-file-service-commands.sgml b/doc/configuration-file-service-commands.sgml index 105064df..02600cf8 100644 --- a/doc/configuration-file-service-commands.sgml +++ b/doc/configuration-file-service-commands.sgml @@ -1,4 +1,6 @@ + Service command settings + repmgr.conf service command settings @@ -7,7 +9,6 @@ service command settings configuration in repmgr.conf - Service command settings In some circumstances, &repmgr; (and &repmgrd;) need to @@ -68,7 +69,7 @@ Do not confuse this with promote_command, which is used - by &repmgrd; to execute . + by &repmgrd; to execute . diff --git a/doc/configuration-file.sgml b/doc/configuration-file.sgml index da104fac..a53effaa 100644 --- a/doc/configuration-file.sgml +++ b/doc/configuration-file.sgml @@ -1,4 +1,7 @@ + + Configuration file + repmgr.conf @@ -8,8 +11,6 @@ repmgr.conf - Configuration file - repmgr and &repmgrd; use a common configuration file, by default called @@ -17,19 +18,19 @@ repmgr.conf 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 + not explicitly supplied. See section for more details. + Configuration file format + repmgr.conf format - Configuration file format - repmgr.conf is a plain text file with one parameter/value combination per line. @@ -63,12 +64,13 @@ data_directory = /var/lib/pgsql/11/data + Configuration file location + repmgr.conf location - Configuration file location The configuration file will be searched for in the following locations: @@ -105,10 +107,10 @@ data_directory = /var/lib/pgsql/11/data If providing the configuration file location with -f/--config-file, - avoid using a relative path, particularly when executing - and , as &repmgr; stores the configuration file location + avoid using a relative path, particularly when executing + and , as &repmgr; stores the configuration file location in the repmgr metadata for use when &repmgr; is executed remotely (e.g. during - ). &repmgr; will attempt to convert the + ). &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. ./repmgr.conf might be converted to /path/to/./repmgr.conf, whereas you'd normally write diff --git a/doc/configuration.sgml b/doc/configuration.sgml index af60ce24..7f7398c4 100644 --- a/doc/configuration.sgml +++ b/doc/configuration.sgml @@ -2,6 +2,8 @@ repmgr configuration + Prerequisites for configuration + configuration prerequisites @@ -12,7 +14,6 @@ ssh - Prerequisites for configuration Following software must be installed on both servers: @@ -62,6 +63,8 @@ + PostgreSQL configuration for &repmgr; + configuration PostgreSQL @@ -71,7 +74,6 @@ PostgreSQL configuration - PostgreSQL configuration for &repmgr; The following PostgreSQL configuration parameters may need to be changed in order for &repmgr; (and replication itself) to function correctly. @@ -81,13 +83,14 @@ - - hot_standby - PostgreSQL configuration - - + + + hot_standby + PostgreSQL configuration + + must always be set to on, as &repmgr; needs to be able to connect to each server it manages. @@ -104,13 +107,15 @@ - - wal_level - PostgreSQL configuration - - + + + + wal_level + PostgreSQL configuration + + must be one of or (PostgreSQL 9.5 and earlier: one of or ). @@ -123,13 +128,15 @@ - - max_wal_senders - PostgreSQL configuration - - + + + + max_wal_senders + PostgreSQL configuration + + must be set to a value of 2 or greater. In general you will need one WAL sender for each standby which will attach to the PostgreSQL @@ -149,13 +156,15 @@ - - max_replication_slots - PostgreSQL configuration - - + + + + max_replication_slots + PostgreSQL configuration + + If you are intending to use replication slots, must be set to a non-zero value. @@ -174,19 +183,20 @@ - - wal_log_hints - PostgreSQL configuration - - + + wal_log_hints + PostgreSQL configuration + + + If you are intending to use pg_rewind, and the cluster was not initialised using data checksums, you may want to consider enabling . - For more details see . + For more details see . PostgreSQL documentation: wal_log_hints. @@ -196,13 +206,15 @@ - - archive_mode - PostgreSQL configuration - - + + + + archive_mode + PostgreSQL configuration + + We suggest setting to on (and to /bin/true; see below) @@ -225,13 +237,15 @@ - - archive_command - PostgreSQL configuration - - + + + + archive_command + PostgreSQL configuration + + If you have set to on but are not currently planning to use WAL file archiving, set to a command which does nothing but returns @@ -246,13 +260,15 @@ - - wal_keep_segments - PostgreSQL configuration - - + + + + wal_keep_segments + PostgreSQL configuration + + Normally there is no need to set (default: 0), as it is not a reliable way of ensuring that all required WAL segments are available to standbys. @@ -293,12 +309,13 @@ &configuration-file-service-commands; + repmgr database user permissions + configuration database user permissions - repmgr database user permissions &repmgr; will create an extension database containing objects for administering &repmgr; metadata. The user defined in the conninfo diff --git a/doc/event-notifications.sgml b/doc/event-notifications.sgml index b2be918e..47c3837f 100644 --- a/doc/event-notifications.sgml +++ b/doc/event-notifications.sgml @@ -1,10 +1,10 @@ + Event Notifications event notifications - Event Notifications Each time &repmgr; or &repmgrd; perform a significant event, a record of that event is written into the repmgr.events table together with @@ -27,7 +27,7 @@ (3 rows) - Alternatively, use to output a + Alternatively, use to output a formatted list of events. @@ -103,10 +103,10 @@ - node ID of the current primary ( and ) + node ID of the current primary ( and ) - node ID of the demoted primary ( only) + node ID of the demoted primary ( only) @@ -115,7 +115,7 @@ conninfo string of the primary node - ( and ) + ( and ) conninfo string of the next available node @@ -128,7 +128,7 @@ - name of the current primary node ( and ) + name of the current primary node ( and ) name of the next available node (bdr_failover and bdr_recovery) diff --git a/doc/follow-new-primary.sgml b/doc/follow-new-primary.sgml index fc9a72c6..f108f46e 100644 --- a/doc/follow-new-primary.sgml +++ b/doc/follow-new-primary.sgml @@ -1,18 +1,19 @@ + Following a new primary + Following a new primary repmgr standby follow - Following a new primary Following the failure or removal of the replication cluster's existing primary - server, can be used to make 'orphaned' standbys + server, can be used to make "orphaned" standbys follow the new primary and catch up to its current state. To demonstrate this, assuming a replication cluster in the same state as the - end of the preceding section (), + end of the preceding section (), execute this: $ repmgr -f /etc/repmgr.conf standby follow diff --git a/doc/install-packages.sgml b/doc/install-packages.sgml index 3102d050..83edcc21 100644 --- a/doc/install-packages.sgml +++ b/doc/install-packages.sgml @@ -13,12 +13,13 @@ + RedHat/CentOS/Fedora + installation on Red Hat/CentOS/Fedora etc. - RedHat/CentOS/Fedora &repmgr; RPM packages for RedHat/CentOS variants and Fedora are available from the 2ndQuadrant @@ -46,7 +47,7 @@ For more information on the package contents, including details of installation paths and relevant service commands, - see the appendix section . + see the appendix section . @@ -105,7 +106,7 @@ sudo yum repolist - Install the &repmgr version appropriate for your PostgreSQL version (e.g. repmgr10): + Install the &repmgr; version appropriate for your PostgreSQL version (e.g. repmgr10): sudo yum install repmgr10 @@ -181,12 +182,13 @@ yum search repmgr + Debian/Ubuntu + installation on Debian/Ubuntu etc. - Debian/Ubuntu .deb packages for &repmgr; are available from the PostgreSQL Community APT repository (http://apt.postgresql.org/). Instructions can be found in the APT section of the PostgreSQL Wiki @@ -195,7 +197,7 @@ yum search repmgr For more information on the package contents, including details of installation paths and relevant service commands, - see the appendix section . + see the appendix section . @@ -242,7 +244,7 @@ curl https://dl.2ndquadrant.com/default/release/get/deb | sudo bash - Install the &repmgr version appropriate for your PostgreSQL version (e.g. repmgr10): + Install the &repmgr; version appropriate for your PostgreSQL version (e.g. repmgr10): sudo apt-get install postgresql-10-repmgr diff --git a/doc/install-requirements.sgml b/doc/install-requirements.sgml index 2362a20a..f554fdc4 100644 --- a/doc/install-requirements.sgml +++ b/doc/install-requirements.sgml @@ -1,11 +1,12 @@ + Requirements for installing repmgr + installation requirements - Requirements for installing repmgr 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 @@ -20,7 +21,7 @@ - If upgrading from &repmgr; 3.x, please see the section . + If upgrading from &repmgr; 3.x, please see the section . @@ -72,6 +73,8 @@ + &repmgr; compatibility matrix + repmgr compatibility matrix @@ -81,7 +84,6 @@ compatibility matrix - &repmgr; compatibility matrix The following table provides an overview of which &repmgr; version supports which PostgreSQL version. diff --git a/doc/install-source.sgml b/doc/install-source.sgml index aa1a3301..6e6362a1 100644 --- a/doc/install-source.sgml +++ b/doc/install-source.sgml @@ -1,11 +1,12 @@ - - installation - from source - Installing &repmgr; from source + + installation + from source + + Prerequisites for installing from source @@ -200,7 +201,7 @@ deb-src http://apt.postgresql.org/pub/repos/apt/ stretch-pgdg mainhttp://repmgr.org/ - for the download information. See + for the download information. See for information on verifying digital signatures. @@ -208,11 +209,11 @@ deb-src http://apt.postgresql.org/pub/repos/apt/ stretch-pgdg mainrepmgr-4.0.tar.gz. You may optionally verify the package checksums from the .md5 files and/or verify the GnuPG signatures - per . + per . - After you unpack the source code archives using tar xf + After you unpack the source code archives using tar xf the installation process is the same as if you were installing from a git clone. @@ -227,7 +228,7 @@ deb-src http://apt.postgresql.org/pub/repos/apt/ stretch-pgdg main - ./configure && make install + ./configure && make install Ensure pg_config for the target PostgreSQL version is in $PATH. @@ -245,7 +246,7 @@ deb-src http://apt.postgresql.org/pub/repos/apt/ stretch-pgdg main PostgreSQL documentation then execute: - ./configure && make install-doc + ./configure && make install-doc The generated HTML files will be placed in the doc/html @@ -255,7 +256,7 @@ deb-src http://apt.postgresql.org/pub/repos/apt/ stretch-pgdg main To build the documentation as a single HTML file, execute: - cd doc/ && make repmgr.html + cd doc/ && make repmgr.html diff --git a/doc/install.sgml b/doc/install.sgml index ce85eb19..ac720acb 100644 --- a/doc/install.sgml +++ b/doc/install.sgml @@ -1,10 +1,11 @@ + + Installation + installation - Installation - &repmgr; can be installed from binary packages provided by your operating system's packaging system, or from source. @@ -18,7 +19,7 @@ only option if there are no packages for your operating system yet. - Before installing &repmgr; make sure you satisfy the . + Before installing &repmgr; make sure you satisfy the . &install-requirements; diff --git a/doc/overview.sgml b/doc/overview.sgml index 1a154151..be63b95e 100644 --- a/doc/overview.sgml +++ b/doc/overview.sgml @@ -7,18 +7,18 @@ + Concepts + concepts - Concepts - 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 - streaming replication. + streaming replication. The following terms are used throughout the &repmgr; documentation. diff --git a/doc/promoting-standby.sgml b/doc/promoting-standby.sgml index 5822f255..7a2deefa 100644 --- a/doc/promoting-standby.sgml +++ b/doc/promoting-standby.sgml @@ -1,13 +1,13 @@ + Promoting a standby server with repmgr promoting a standby repmgr standby promote - Promoting a standby server with repmgr 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 , + to function correctly. This can be done with , which promotes the standby on the current server to primary. @@ -31,7 +31,7 @@ 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 will note the discrepancy: + executing will note the discrepancy: $ repmgr -f /etc/repmgr.conf cluster show ID | Name | Role | Status | Upstream | Location | Connection string @@ -60,7 +60,7 @@ DETAIL: node 2 was successfully promoted to primary - Executing will show the current state; as there is now an + Executing will show the current state; as there is now an active primary, the previous warning will not be displayed: $ repmgr -f /etc/repmgr.conf cluster show @@ -72,8 +72,8 @@ However the sole remaining standby (node3) is still trying to replicate from the failed - primary; must now be executed to rectify this situation - (see for example). + primary; must now be executed to rectify this situation + (see for example). diff --git a/doc/quickstart.sgml b/doc/quickstart.sgml index ad4f7894..e89ffa50 100644 --- a/doc/quickstart.sgml +++ b/doc/quickstart.sgml @@ -17,7 +17,7 @@ To upgrade an existing &repmgr; 3.x installation, see section - . + . @@ -139,7 +139,7 @@ Additionally, if you are intending to use pg_rewind, and the cluster was not initialised using data checksums, you may want to consider enabling - wal_log_hints; for more details see . + wal_log_hints; for more details see . See also the PostgreSQL configuration section in the @@ -262,7 +262,7 @@ repmgr.conf should not be stored inside the PostgreSQL data directory, as it could be overwritten when setting up or reinitialising the PostgreSQL - server. See sections and + server. See sections and for further details about repmgr.conf. @@ -303,7 +303,7 @@ See the file - repmgr.conf.sample + repmgr.conf.sample for details of all available configuration parameters. diff --git a/doc/repmgr-cluster-cleanup.sgml b/doc/repmgr-cluster-cleanup.sgml index c2b70967..ef14804b 100644 --- a/doc/repmgr-cluster-cleanup.sgml +++ b/doc/repmgr-cluster-cleanup.sgml @@ -69,8 +69,8 @@ See also - For more details see the sections and - . + For more details see the sections and + . diff --git a/doc/repmgr-cluster-crosscheck.sgml b/doc/repmgr-cluster-crosscheck.sgml index d730b217..ac611aa8 100644 --- a/doc/repmgr-cluster-crosscheck.sgml +++ b/doc/repmgr-cluster-crosscheck.sgml @@ -16,9 +16,9 @@ Description - repmgr cluster crosscheck is similar to , + repmgr cluster crosscheck is similar to , but cross-checks connections between each combination of nodes. In "Example 3" in - we have no information about the state of node3. + we have no information about the state of node3. However by running repmgr cluster crosscheck it's possible to get a better overview of the cluster situation: diff --git a/doc/repmgr-cluster-event.sgml b/doc/repmgr-cluster-event.sgml index 9281ba80..d953bb67 100644 --- a/doc/repmgr-cluster-event.sgml +++ b/doc/repmgr-cluster-event.sgml @@ -40,7 +40,7 @@ --node-name: restrict entries to node with this name - --event: filter specific event (see for a full list) + --event: filter specific event (see for a full list) diff --git a/doc/repmgr-cluster-matrix.sgml b/doc/repmgr-cluster-matrix.sgml index 604bddb6..a0ba728a 100644 --- a/doc/repmgr-cluster-matrix.sgml +++ b/doc/repmgr-cluster-matrix.sgml @@ -93,7 +93,7 @@ connection from node3. - In this case, the command will produce a more + In this case, the command will produce a more useful result. diff --git a/doc/repmgr-cluster-show.sgml b/doc/repmgr-cluster-show.sgml index f09b9926..196d9b87 100644 --- a/doc/repmgr-cluster-show.sgml +++ b/doc/repmgr-cluster-show.sgml @@ -26,7 +26,7 @@ Node availability is tested by connecting from the node where repmgr cluster show is executed, and does not necessarily imply the node - is down. See and to get + is down. See and to get better overviews of connections between nodes. @@ -101,7 +101,7 @@ - Use and + Use and to diagnose connection issues across the whole replication cluster. @@ -231,7 +231,7 @@ See also - , , + , , diff --git a/doc/repmgr-daemon-pause.sgml b/doc/repmgr-daemon-pause.sgml index aab59d92..6a83b476 100644 --- a/doc/repmgr-daemon-pause.sgml +++ b/doc/repmgr-daemon-pause.sgml @@ -37,7 +37,7 @@ - will instruct all previously paused &repmgrd; + will instruct all previously paused &repmgrd; instances to resume normal failover operation. @@ -107,7 +107,7 @@ NOTICE: node 3 (node3) paused See also - , + , diff --git a/doc/repmgr-daemon-start.sgml b/doc/repmgr-daemon-start.sgml index 7618ee37..ee2f1136 100644 --- a/doc/repmgr-daemon-start.sgml +++ b/doc/repmgr-daemon-start.sgml @@ -33,7 +33,7 @@ The repmgr.conf parameter repmgrd_service_start_command must be set for repmgr daemon start to work; see section - for details. + for details. @@ -99,13 +99,14 @@ - - repmgrd_service_start_command - with "repmgr daemon start" - + + repmgrd_service_start_command + with "repmgr daemon start" + + repmgr daemon start will execute the command defined by the repmgrd_service_start_command parameter in repmgr.conf. @@ -196,7 +197,7 @@ See also - , , + , , diff --git a/doc/repmgr-daemon-status.sgml b/doc/repmgr-daemon-status.sgml index 9e35c393..5c8c40b7 100644 --- a/doc/repmgr-daemon-status.sgml +++ b/doc/repmgr-daemon-status.sgml @@ -22,7 +22,7 @@ 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 and + the result of and operations. @@ -60,7 +60,7 @@ - &repmgrd; paused on all nodes (using ): + &repmgrd; paused on all nodes (using ): $ repmgr -f /etc/repmgr.conf daemon status ID | Name | Role | Status | Upstream | repmgrd | PID | Paused? | Upstream last seen ----+-------+---------+-----------+----------+---------+-------+---------+-------------------- @@ -192,7 +192,7 @@ See also - , , + , , diff --git a/doc/repmgr-daemon-stop.sgml b/doc/repmgr-daemon-stop.sgml index e282ef89..6ff2f8ef 100644 --- a/doc/repmgr-daemon-stop.sgml +++ b/doc/repmgr-daemon-stop.sgml @@ -40,7 +40,7 @@ The repmgr.conf parameter repmgrd_service_stop_command must be set for repmgr daemon stop to work; see section - for details. + for details. @@ -124,13 +124,14 @@ - - repmgrd_service_stop_command - with "repmgr daemon stop" - + + repmgrd_service_stop_command + with "repmgr daemon stop" + + repmgr daemon stop will execute the command defined by the repmgrd_service_stop_command parameter in repmgr.conf. @@ -193,7 +194,7 @@ See also - , , + , , diff --git a/doc/repmgr-daemon-unpause.sgml b/doc/repmgr-daemon-unpause.sgml index cd507303..ed77e330 100644 --- a/doc/repmgr-daemon-unpause.sgml +++ b/doc/repmgr-daemon-unpause.sgml @@ -23,7 +23,7 @@ This command can be run on any active node in the replication cluster to instruct all running &repmgrd; instances to "unpause" - (following a previous execution of ) + (following a previous execution of ) and resume normal failover/monitoring operation. @@ -102,7 +102,7 @@ NOTICE: node 3 (node3) unpaused See also - , + , diff --git a/doc/repmgr-node-check.sgml b/doc/repmgr-node-check.sgml index 4c1d908b..e7d94ce4 100644 --- a/doc/repmgr-node-check.sgml +++ b/doc/repmgr-node-check.sgml @@ -203,7 +203,7 @@ See also - , + , diff --git a/doc/repmgr-node-rejoin.sgml b/doc/repmgr-node-rejoin.sgml index 317348b5..e5ddf11e 100644 --- a/doc/repmgr-node-rejoin.sgml +++ b/doc/repmgr-node-rejoin.sgml @@ -26,10 +26,10 @@ If the node is running and needs to be attached to the current primary, use - . + . - Note can only be used for standbys which have not diverged + Note can only be used for standbys which have not diverged from the rest of the cluster. @@ -230,12 +230,13 @@ + Using <command>pg_rewind</command> + pg_rewind using with "repmgr node rejoin" - Using <command>pg_rewind</command> repmgr node rejoin can optionally use pg_rewind to re-integrate a node which has diverged from the rest of the cluster, typically a failed primary. @@ -321,7 +322,7 @@ If is used with the option, this checks the prerequisites for using pg_rewind, but is not an absolute guarantee that actually executing pg_rewind - will succeed. See also section below. + will succeed. See also section below. @@ -344,12 +345,13 @@ - - repmgr node rejoin - caveats - - Caveats when using <command>repmgr node rejoin</command> + + + repmgr node rejoin + caveats + + repmgr node rejoin attempts to determine whether it will succeed by comparing the timelines and relative WAL positions of the local node (rejoin candidate) and primary @@ -381,7 +383,7 @@ See also - + diff --git a/doc/repmgr-node-status.sgml b/doc/repmgr-node-status.sgml index 20d75bf8..6c6f0068 100644 --- a/doc/repmgr-node-status.sgml +++ b/doc/repmgr-node-status.sgml @@ -84,7 +84,7 @@ See also - See to diagnose issues and + See to diagnose issues and for an overview of all nodes in the cluster. diff --git a/doc/repmgr-primary-register.sgml b/doc/repmgr-primary-register.sgml index d523fbc7..7796fa85 100644 --- a/doc/repmgr-primary-register.sgml +++ b/doc/repmgr-primary-register.sgml @@ -44,7 +44,7 @@ If providing the configuration file location with , 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 - ). &repmgr; will attempt to convert the + ). &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. ./repmgr.conf might be converted to /path/to/./repmgr.conf, whereas you'd normally write diff --git a/doc/repmgr-standby-clone.sgml b/doc/repmgr-standby-clone.sgml index 32dabe3d..a4cd8a5b 100644 --- a/doc/repmgr-standby-clone.sgml +++ b/doc/repmgr-standby-clone.sgml @@ -85,12 +85,13 @@ - + Customising recovery.conf + recovery.conf customising with "repmgr standby clone" - + + - Customising recovery.conf By default, &repmgr; will create a minimal recovery.conf containing following parameters: @@ -142,7 +143,7 @@ We recommend using Barman to manage WAL file archiving. For more details on combining &repmgr; and Barman, in particular using restore_command to configure Barman as a backup source of - WAL files, see . + WAL files, see . @@ -186,12 +187,13 @@ + Using a standby cloned by another method + recovery.conf generating for a standby cloned by another method - Using a standby cloned by another method &repmgr; supports standbys cloned by another method (e.g. using barman's barman recover command). @@ -296,7 +298,7 @@ - Create recovery.conf file for a previously cloned instance. &repmgr 4.0.4 and later. + Create recovery.conf file for a previously cloned instance. &repmgr; 4.0.4 and later. @@ -361,7 +363,7 @@ See also - See for details about various aspects of cloning. + See for details about various aspects of cloning. diff --git a/doc/repmgr-standby-follow.sgml b/doc/repmgr-standby-follow.sgml index 9f3815dd..6ff8e306 100644 --- a/doc/repmgr-standby-follow.sgml +++ b/doc/repmgr-standby-follow.sgml @@ -41,7 +41,7 @@ To re-add an inactive node to the replication cluster, use - . + . @@ -252,7 +252,7 @@ DETAIL: follow target server's timeline 2 forked off current database system tim See also - + diff --git a/doc/repmgr-standby-register.sgml b/doc/repmgr-standby-register.sgml index 42b647c7..01ed1079 100644 --- a/doc/repmgr-standby-register.sgml +++ b/doc/repmgr-standby-register.sgml @@ -28,7 +28,7 @@ If providing the configuration file location with -f/--config-file, 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 - ). &repmgr; will attempt to convert the + ). &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. ./repmgr.conf might be converted to /path/to/./repmgr.conf, whereas you'd normally write diff --git a/doc/repmgr-standby-switchover.sgml b/doc/repmgr-standby-switchover.sgml index 93f52a9a..2b772aed 100644 --- a/doc/repmgr-standby-switchover.sgml +++ b/doc/repmgr-standby-switchover.sgml @@ -44,7 +44,7 @@ For more details on performing a switchover, including preparation and configuration, - see section . + see section . @@ -52,7 +52,7 @@ From repmgr 4.2, &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 . + unintentionally promoting a node. For more details, see . Users of &repmgr; versions prior to 4.2 should ensure that &repmgrd; @@ -117,7 +117,7 @@ (and the prerequisites for using pg_rewind are met). If using PostgreSQL 9.3 or 9.4, and the pg_rewind binary is not installed in the PostgreSQL bin directory, - provide its full path. For more details see also . + provide its full path. For more details see also . @@ -181,13 +181,14 @@ - - replication_lag_critical - with "repmgr standby switchover" - - + + + replication_lag_critical + with "repmgr standby switchover" + + If replication lag (in seconds) on the standby exceeds this value, the switchover will be aborted (unless the -F/--force option @@ -197,13 +198,14 @@ - - shutdown_check_timeout - with "repmgr standby switchover" - + + shutdown_check_timeout + with "repmgr standby switchover" + + The maximum number of seconds to wait for the demotion candidate (current primary) to shut down, before aborting the switchover. @@ -225,13 +227,13 @@ - - wal_receive_check_timeout - with "repmgr standby switchover" - - + + wal_receive_check_timeout + with "repmgr standby switchover" + + 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 @@ -242,13 +244,14 @@ - - standby_reconnect_timeout - with "repmgr standby switchover" - + + standby_reconnect_timeout + with "repmgr standby switchover" + + The maximum number of seconds to attempt to wait for the demotion candidate (former primary) to reconnect to the promoted primary (default: 60 seconds) @@ -261,14 +264,16 @@ - - - node_rejoin_timeout - with "repmgr standby switchover" - + + + + node_rejoin_timeout + with "repmgr standby switchover" + + maximum number of seconds to attempt to wait for the demotion candidate (former primary) to reconnect to the promoted primary (default: 60 seconds) @@ -362,10 +367,10 @@ See also - , + , - For more details on performing a switchover operation, see the section . + For more details on performing a switchover operation, see the section . diff --git a/doc/repmgr.sgml b/doc/repmgr.sgml index 7238c574..13206def 100644 --- a/doc/repmgr.sgml +++ b/doc/repmgr.sgml @@ -1,7 +1,8 @@ - %version; @@ -38,7 +39,7 @@ &repmgr; is developed by 2ndQuadrant - along with contributions from other individuals and companies. + along with contributions from other individuals and organisations. Contributions from the community are appreciated and welcome - get in touch via github or the mailing list/forum. @@ -128,7 +129,6 @@ &appendix-packages; &appendix-support; - - ]]> + diff --git a/doc/repmgrd-automatic-failover.sgml b/doc/repmgrd-automatic-failover.sgml index f79389eb..7256ca46 100644 --- a/doc/repmgrd-automatic-failover.sgml +++ b/doc/repmgrd-automatic-failover.sgml @@ -1,11 +1,12 @@ + + Automatic failover with repmgrd + repmgrd automatic failover - Automatic failover with repmgrd - &repmgrd; is a management and monitoring daemon which runs on each node in a replication cluster. It can automate actions such as @@ -13,7 +14,9 @@ providing monitoring information about the state of each standby. - + + Using a witness server + repmgrd witness server @@ -23,9 +26,9 @@ witness server repmgrd - Using a witness server + - A is a normal PostgreSQL instance which + A 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 @@ -55,7 +58,7 @@ 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 for more details. + see for more details. @@ -85,10 +88,10 @@ The witness server should be configured in the same way as a normal - &repmgr; node; see section . + &repmgr; node; see section . - Register the witness server with . + Register the witness server with . This will create the &repmgr; extension on the witness server, and make a copy of the &repmgr; metadata. @@ -105,7 +108,7 @@ - To unregister a witness server, use . + To unregister a witness server, use . @@ -114,6 +117,7 @@ + Handling network splits with repmgrd repmgrd network splits @@ -123,7 +127,6 @@ network splits - Handling network splits with repmgrd A common pattern for replication cluster setups is to spread servers over more than one datacentre. This can provide benefits such as geographically- @@ -134,7 +137,7 @@ in the main data centre and promoted a standby among themselves. - &repmgr; enables provision of "" to + &repmgr; enables provision of "" 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 @@ -166,6 +169,8 @@ + Monitoring standby disconnections on the primary node + repmgrd standby disconnection @@ -176,11 +181,9 @@ child node disconnection - Monitoring standby disconnections on the primary node - - This functionality is available in &repmgr 4.4 and later. + This functionality is available in &repmgr; 4.4 and later. @@ -367,12 +370,13 @@ - - child_nodes_check_interval - child node disconnection monitoring - child_nodes_check_interval + + child_nodes_check_interval + child node disconnection monitoring + + Interval (in seconds) after which &repmgrd; queries the pg_stat_replication system view and compares the nodes present @@ -386,12 +390,14 @@ - - child_nodes_disconnect_command - child node disconnection monitoring - child_nodes_disconnect_command + + + child_nodes_disconnect_command + child node disconnection monitoring + + User-definable script to be executed when &repmgrd; determines that an insufficient number of child nodes are connected. By default @@ -442,12 +448,14 @@ - - child_nodes_disconnect_timeout - child node disconnection monitoring - child_nodes_disconnect_timeout + + + child_nodes_disconnect_timeout + child node disconnection monitoring + + If &repmgrd; determines that an insufficient number of child nodes are connected, it will wait for the specified number of seconds @@ -460,12 +468,13 @@ - - child_nodes_connected_min_count - child node disconnection monitoring - child_nodes_connected_min_count + + child_nodes_connected_min_count + child node disconnection monitoring + + If the number of child nodes connected falls below the number specified in this parameter, the child_nodes_disconnect_command script @@ -492,12 +501,13 @@ - - child_nodes_disconnect_min_count - child node disconnection monitoring - child_nodes_disconnect_min_count + + child_nodes_disconnect_min_count + child node disconnection monitoring + + If the number of disconnected child nodes exceeds the number specified in this parameter, the child_nodes_disconnect_command script @@ -536,12 +546,13 @@ - - child_node_disconnect - event notification - child_node_disconnect + + child_node_disconnect + event notification + + This event is generated after &repmgrd; detects that a child node is no longer streaming from the primary node. @@ -558,12 +569,13 @@ $ repmgr cluster event --event=child_node_disconnect - - child_node_reconnect - event notification - child_node_reconnect + + child_node_reconnect + event notification + + This event is generated after &repmgrd; detects that a child node has resumed streaming from the primary node. @@ -580,12 +592,13 @@ $ repmgr cluster event --event=child_node_reconnect - - child_node_new_connect - event notification - child_node_new_connect + + child_node_new_connect + event notification + + This event is generated after &repmgrd; detects that a new child node has been registered with &repmgr; and has @@ -603,12 +616,13 @@ $ repmgr cluster event --event=child_node_new_connect - - child_nodes_disconnect_command - event notification - child_nodes_disconnect_command + + child_nodes_disconnect_command + event notification + + This event is generated after &repmgrd; detects that sufficient child nodes have been disconnected for a sufficient amount @@ -633,6 +647,8 @@ $ repmgr cluster event --event=child_nodes_disconnect_command + Standby disconnection on failover + repmgrd standby disconnection on failover @@ -642,7 +658,6 @@ $ repmgr cluster event --event=child_nodes_disconnect_command standby disconnection on failover - Standby disconnection on failover If is set to true in repmgr.conf, in a failover situation &repmgrd; will forcibly disconnect @@ -680,6 +695,8 @@ $ repmgr cluster event --event=child_nodes_disconnect_command + Failover validation + repmgrd failover validation @@ -689,7 +706,6 @@ $ repmgr cluster event --event=child_nodes_disconnect_command failover validation - Failover validation From repmgr 4.3, &repmgr; makes it possible to provide a script to &repmgrd; which, in a failover situation, @@ -733,18 +749,19 @@ INFO: node 3 received notification to rerun promotion candidate election - - + + repmgrd and cascading replication + + repmgrd cascading replication - + cascading replication repmgrd - repmgrd and cascading replication 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 diff --git a/doc/repmgrd-bdr.sgml b/doc/repmgrd-bdr.sgml index a3bff566..bae11e98 100644 --- a/doc/repmgrd-bdr.sgml +++ b/doc/repmgrd-bdr.sgml @@ -1,4 +1,6 @@ + BDR failover with repmgrd + repmgrd BDR @@ -8,7 +10,6 @@ BDR - BDR failover with repmgrd &repmgr; 4.x provides support for monitoring a pair of BDR 2.x nodes and taking action in case one of the nodes fails. @@ -94,7 +95,7 @@ # Event notification configuration event_notifications=bdr_failover - event_notification_command='/path/to/bdr-pgbouncer.sh %n %e %s "%c" "%a" >> /tmp/bdr-failover.log 2>&1' + 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 @@ -120,7 +121,7 @@ event_notification_command is the script which does the actual "heavy lifting" of reconfiguring the proxy server/ connection pooler. It is fully - user-definable; see section for a reference + user-definable; see section for a reference implementation. @@ -158,7 +159,7 @@ At this point the meta data for both nodes has been created; executing - (on either node) should produce output like this: + (on either node) should produce output like this: $ repmgr -f /etc/repmgr.conf cluster show ID | Name | Role | Status | Upstream | Location | Connection string @@ -168,7 +169,7 @@ Additionally it's possible to display log of significant events; executing - (on either node) should produce output like this: + (on either node) should produce output like this: $ repmgr -f /etc/repmgr.conf cluster event Node ID | Event | OK | Timestamp | Details diff --git a/doc/repmgrd-configuration.sgml b/doc/repmgrd-configuration.sgml index 8d8fe64c..a0fbb370 100644 --- a/doc/repmgrd-configuration.sgml +++ b/doc/repmgrd-configuration.sgml @@ -1,12 +1,12 @@ + repmgrd setup and configuration + repmgrd configuration - repmgrd setup and configuration - &repmgrd; is a daemon which runs on each PostgreSQL node, monitoring the local node, and (unless it's the primary node) the upstream server @@ -39,108 +39,111 @@ - - - + + + + monitor_interval_secs - - - - The interval (in seconds, default: 2) to check the availability of the upstream node. - - - + + The interval (in seconds, default: 2) to check the availability of the upstream node. + + - + + + + + connection_check_type - - - - The option is used to select the method - &repmgrd; uses to determine whether the upstream node is available. - - - Possible values are: - - + + + The option is used to select the method + &repmgrd; uses to determine whether the upstream node is available. + + + Possible values are: + + ping (default) - uses PQping() to determine server availability - - - - connection - determines server availability - by attempt ingto make a new connection to the upstream node - - - - - query - determines server availability - by executing an SQL statement on the node via the existing connection - - + + + + connection - determines server availability + by attempt ingto make a new connection to the upstream node + + + + + query - determines server availability + by executing an SQL statement on the node via the existing connection + + - - - - + + + + - - + + + + reconnect_attempts - - - - The number of attempts (default: 6) will be made to reconnect to an unreachable - upstream node before initiating a failover. - - - There will be an interval of seconds between each reconnection - attempt. - - - - - + + The number of attempts (default: 6) will be made to reconnect to an unreachable + upstream node before initiating a failover. + + + There will be an interval of seconds between each reconnection + attempt. + + + + + + + + + reconnect_interval - - - - Interval (in seconds, default: 10) between attempts to reconnect to an unreachable - upstream node. - - + + + Interval (in seconds, default: 10) between attempts to reconnect to an unreachable + upstream node. + + The number of reconnection attempts is defined by the parameter . - - - + + + - - - + + + degraded_monitoring_timeout - - - - Interval (in seconds) after which &repmgrd; will terminate if - either of the servers (local node and or upstream node) being monitored is no longer available - (degraded monitoring mode). - - - -1 (default) disables this timeout completely. - - - + + + Interval (in seconds) after which &repmgrd; will terminate if + either of the servers (local node and or upstream node) being monitored is no longer available + (degraded monitoring mode). + + + -1 (default) disables this timeout completely. + + + @@ -182,11 +185,12 @@ - - failover - + + failover + + can be one of automatic or manual. @@ -202,11 +206,13 @@ - - promote_command - + + + promote_command + + The program or script defined in will be executed in a failover situation when &repmgrd; determines that @@ -245,11 +251,12 @@ - - follow_command - + + follow_command + + The program or script defined in will be executed in a failover situation when &repmgrd; determines that @@ -312,11 +319,12 @@ - - priority - + + priority + + Indicates a preferred priority (default: 100) for promoting nodes; a value of zero prevents the node being promoted to primary. @@ -330,11 +338,12 @@ - - failover_validation_command - + + failover_validation_command + + User-defined script to execute for an external mechanism to validate the failover decision made by &repmgrd;. @@ -366,12 +375,13 @@ - - - primary_visibility_consensus - + + + primary_visibility_consensus + + If true, only continue with failover if no standbys have seen the primary node recently. @@ -387,11 +397,12 @@ - - standby_disconnect_on_failover - + + standby_disconnect_on_failover + + In a failover situation, disconnect the local node's WAL receiver. @@ -429,11 +440,12 @@ - - election_rerun_interval - + + election_rerun_interval + + If is set, and the command returns an error, pause the specified amount of seconds (default: 15) before rerunning the election. @@ -443,11 +455,12 @@ - - sibling_nodes_disconnect_timeout - + + sibling_nodes_disconnect_timeout + + If is true, the maximum length of time (in seconds, default: 30) @@ -463,11 +476,12 @@ + PostgreSQL service configuration + repmgrd PostgreSQL service configuration - PostgreSQL service configuration If using automatic failover, currently &repmgrd; will need to execute repmgr standby follow @@ -481,16 +495,17 @@ particularly on systemd-based systems. - For more details, see . + For more details, see . + repmgrd service configuration + repmgrd repmgrd service configuration - repmgrd service configuration If you are intending to use the repmgr daemon start and repmgr daemon stop commands, the following @@ -522,11 +537,12 @@ repmgrd_service_stop_command='sudo systemctl repmgr11 stop' + Monitoring configuration + repmgrd monitoring configuration - Monitoring configuration To enable monitoring, set: @@ -538,20 +554,21 @@ repmgrd_service_stop_command='sudo systemctl repmgr11 stop' the option (see above). - For more details on monitoring, see . + For more details on monitoring, see . - + + Applying configuration changes to repmgrd + repmgrd applying configuration changes - Applying configuration changes to repmgrd To apply configuration file changes to a running &repmgrd; daemon, execute the operating system's &repmgrd; service reload command - (see for examples), + (see for examples), or for instances which were manually started, execute kill -HUP, e.g. kill -HUP `cat /tmp/repmgrd.pid`. @@ -779,18 +796,19 @@ repmgrd_service_stop_command='sudo systemctl repmgr11 stop' + repmgrd daemon + repmgrd starting and stopping - repmgrd daemon If installed from a package, the &repmgrd; can be started via the operating system's service command, e.g. in systemd using systemctl. - See appendix for details of service commands + See appendix for details of service commands for different distributions. @@ -815,6 +833,8 @@ repmgrd_service_stop_command='sudo systemctl repmgr11 stop' + repmgrd's PID file + repmgrd PID file @@ -823,7 +843,6 @@ repmgrd_service_stop_command='sudo systemctl repmgr11 stop' PID file repmgrd - repmgrd's PID file &repmgrd; will generate a PID file by default. @@ -868,6 +887,8 @@ repmgrd_service_stop_command='sudo systemctl repmgr11 stop' + repmgrd daemon configuration on Debian/Ubuntu + repmgrd Debian/Ubuntu and daemon configuration @@ -877,8 +898,6 @@ repmgrd_service_stop_command='sudo systemctl repmgr11 stop' repmgrd daemon configuration - repmgrd daemon configuration on Debian/Ubuntu - If &repmgr; was installed from Debian/Ubuntu packages, additional configuration is required before &repmgrd; is started as a daemon. @@ -915,7 +934,7 @@ REPMGRD_OPTS="--daemonize=false" - See for details of the Debian/Ubuntu packages and + See for details of the Debian/Ubuntu packages and typical file locations (including repmgr.conf). @@ -959,7 +978,9 @@ REPMGRD_OPTS="--daemonize=false" - + + repmgrd log rotation + log rotation repmgrd @@ -970,7 +991,6 @@ REPMGRD_OPTS="--daemonize=false" log rotation - repmgrd log rotation To ensure the current &repmgrd; logfile (specified in repmgr.conf with the parameter diff --git a/doc/repmgrd-operation.sgml b/doc/repmgrd-operation.sgml index 37e331b7..9cbf5ede 100644 --- a/doc/repmgrd-operation.sgml +++ b/doc/repmgrd-operation.sgml @@ -1,14 +1,15 @@ + repmgrd operation + repmgrd operation - repmgrd operation - - + Pausing repmgrd + repmgrd pausing @@ -18,7 +19,6 @@ pausing repmgrd - Pausing repmgrd In normal operation, &repmgrd; monitors the state of the @@ -185,12 +185,13 @@ NOTICE: node 3 (node3) unpaused + repmgrd and paused WAL replay + repmgrd paused WAL replay - repmgrd and paused WAL replay If WAL replay has been paused (using pg_wal_replay_pause(), on PostgreSQL 9.6 and earlier pg_xlog_replay_pause()), @@ -214,6 +215,8 @@ NOTICE: node 3 (node3) unpaused + "degraded monitoring" mode + repmgrd degraded monitoring @@ -223,7 +226,6 @@ NOTICE: node 3 (node3) unpaused degraded monitoring - "degraded monitoring" mode In certain circumstances, &repmgrd; is not able to fulfill its primary mission of monitoring the node's upstream server. In these cases it enters "degraded monitoring" @@ -302,6 +304,7 @@ NOTICE: node 3 (node3) unpaused + Storing monitoring data repmgrd monitoring @@ -311,7 +314,6 @@ NOTICE: node 3 (node3) unpaused with repmgrd - Storing monitoring data When &repmgrd; is running with the option monitoring_history=true, it will constantly write standby node status information to the @@ -346,7 +348,7 @@ NOTICE: node 3 (node3) unpaused As this can generate a large amount of monitoring data in the table repmgr.monitoring_history. it's advisable to regularly - purge historical data using the + purge historical data using the command; use the -k/--keep-history option to specify how many day's worth of data should be retained. diff --git a/doc/repmgrd-overview.sgml b/doc/repmgrd-overview.sgml index edc139af..a40d00be 100644 --- a/doc/repmgrd-overview.sgml +++ b/doc/repmgrd-overview.sgml @@ -1,11 +1,11 @@ + repmgrd overview + repmgrd overview - repmgrd overview - &repmgrd; ("replication manager daemon") is a management and monitoring daemon which runs diff --git a/doc/stylesheet-common.xsl b/doc/stylesheet-common.xsl new file mode 100644 index 00000000..77219028 --- /dev/null +++ b/doc/stylesheet-common.xsl @@ -0,0 +1,89 @@ + + + + + + + + + + + + + + 1 + 0 + + + + +2 + + + + + + + + + +1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + ? + + ? + + + diff --git a/doc/stylesheet-html-common.xsl b/doc/stylesheet-html-common.xsl new file mode 100644 index 00000000..9edce52a --- /dev/null +++ b/doc/stylesheet-html-common.xsl @@ -0,0 +1,292 @@ + + +%common.entities; +]> + + + + + + + + +pgsql-docs@lists.postgresql.org +2 + + + + + + + + + + + + + + , + + + + + + + + + + ISBN + + + + + + + + + +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 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +

+ + + + + + + + + + + + +

+ + + + + + +
+

+ + + +

+
+ + + + + + + +
+
+ + + + + + +
+

+ + + +

+
+ + + + + + + +
+
+ + + + + + + + + + + +
+ + + + + + + + + + +
+ + + + + + +

+ +

+ +
+ + + + + + + +
+
+ + + + + + + + + + + + + + | + + + + + + + + + + + + + + + + + + + + + + + + + + id- + + + + + + + + + + diff --git a/doc/stylesheet-speedup-common.xsl b/doc/stylesheet-speedup-common.xsl new file mode 100644 index 00000000..e3fb582a --- /dev/null +++ b/doc/stylesheet-speedup-common.xsl @@ -0,0 +1,100 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +en + + diff --git a/doc/stylesheet-speedup-xhtml.xsl b/doc/stylesheet-speedup-xhtml.xsl new file mode 100644 index 00000000..da0f2b5a --- /dev/null +++ b/doc/stylesheet-speedup-xhtml.xsl @@ -0,0 +1,345 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + , + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Error: If you change $chunk.section.depth, then you must update the performance-optimized chunk-all-sections-template. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/doc/stylesheet.xsl b/doc/stylesheet.xsl new file mode 100644 index 00000000..4ff6e8ed --- /dev/null +++ b/doc/stylesheet.xsl @@ -0,0 +1,174 @@ + + + + + + + + + + + + + + + + + + + + + + stylesheet.css + https://www.postgresql.org/media/css/docs.css + + + + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + + + + + + + + + + +
+ +
+ + + + + + + + + + + + + + + +   + + + + + + + + + + + + + + + + + +   + + + + + + +   + + + + + + + + + + + + + + + + + + +  |  + + +   + + +   + + + + + + + + + + + + + + + +
+ + +
+ +
+ + + + diff --git a/doc/switchover.sgml b/doc/switchover.sgml index 235c746b..a987cdc5 100644 --- a/doc/switchover.sgml +++ b/doc/switchover.sgml @@ -1,10 +1,10 @@ + Performing a switchover with repmgr switchover - Performing a switchover with repmgr 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 @@ -15,7 +15,7 @@ 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 command. + is supported by the command. repmgr standby switchover differs from other &repmgr; @@ -44,17 +44,18 @@ and capturing all output to assist troubleshooting any problems. - Please also read carefully the sections and - below. + Please also read carefully the sections and + below. + Preparing for switchover + switchover preparation - Preparing for switchover As mentioned in the previous section, success of the switchover operation depends on @@ -114,7 +115,7 @@ server. - For more details, see . + For more details, see . @@ -161,7 +162,7 @@ From repmgr 4.2, &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 . + unintentionally promoting a node. For more details, see . Users of &repmgr; versions prior to 4.2 should ensure that &repmgrd; @@ -204,18 +205,19 @@ - See for a full list of available + See for a full list of available command line options and repmgr.conf settings relevant to performing a switchover. - + + Switchover and pg_rewind + pg_rewind using with "repmgr standby switchover" - Switchover and pg_rewind 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 @@ -258,11 +260,12 @@ + Executing the switchover command + switchover execution - Executing the switchover command To demonstrate switchover, we will assume a replication cluster with a primary (node1) and one standby (node2); @@ -328,11 +331,11 @@ + Caveats switchover caveats - Caveats @@ -357,11 +360,12 @@ + Troubleshooting switchover issues + switchover troubleshooting - Troubleshooting switchover issues As emphasised previously, performing a switchover diff --git a/doc/upgrading-repmgr.sgml b/doc/upgrading-repmgr.sgml index 8a738369..a6454625 100644 --- a/doc/upgrading-repmgr.sgml +++ b/doc/upgrading-repmgr.sgml @@ -1,10 +1,10 @@ + Upgrading repmgr upgrading - Upgrading repmgr &repmgr; is updated regularly with minor releases (e.g. 4.0.1 to 4.0.2) @@ -13,11 +13,12 @@ + Upgrading repmgr 4.x and later + upgrading repmgr 4.x and later - Upgrading repmgr 4.x and later From version 4, &repmgr; consists of three elements: @@ -63,11 +64,12 @@ + Upgrading a minor version release + upgrading minor release - Upgrading a minor version release The process for installing minor version upgrades is quite straightforward: @@ -118,11 +120,13 @@ + Upgrading a major version release + upgrading major release - Upgrading a major version release + "major version" 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 @@ -205,11 +209,12 @@ ALTER EXTENSION repmgr UPDATE + Checking repmgrd status after an upgrade + upgrading checking repmgrd status - Checking repmgrd status after an upgrade From repmgr 4.2, once the upgrade is complete, execute the repmgr daemon status command (on any node) to show an overview of the status of &repmgrd; on all nodes. @@ -218,6 +223,8 @@ ALTER EXTENSION repmgr UPDATE + pg_upgrade and repmgr + upgrading pg_upgrade @@ -225,7 +232,6 @@ ALTER EXTENSION repmgr UPDATE pg_upgrade - pg_upgrade and repmgr pg_upgrade requires that if any functions are @@ -265,12 +271,13 @@ ALTER EXTENSION repmgr UPDATE + Upgrading from repmgr 3.x + upgrading from repmgr 3.x - Upgrading from repmgr 3.x The upgrade process consists of two steps: @@ -383,7 +390,7 @@ ALTER EXTENSION repmgr UPDATE to the server configured in Barman (in &repmgr; 3, the deprecated cluster parameter was used for this); the physical Barman hostname is configured with - barman_host (see + barman_host (see for details).