pax_global_header00006660000000000000000000000064130636632640014523gustar00rootroot0000000000000052 comment=9c28d3626badfdcb9c8fb7002e7f5c39901c4d4d repmgr-3.3.1/000077500000000000000000000000001306366326400130235ustar00rootroot00000000000000repmgr-3.3.1/.gitignore000066400000000000000000000001331306366326400150100ustar00rootroot00000000000000*~ *.o *.so repmgr repmgrd README.htm* README.pdf sql/repmgr_funcs.so sql/repmgr_funcs.sql repmgr-3.3.1/CONTRIBUTING.md000066400000000000000000000023321306366326400152540ustar00rootroot00000000000000License and Contributions ========================= `repmgr` is licensed under the GPL v3. All of its code and documentation is Copyright 2010-2017, 2ndQuadrant Limited. See the files COPYRIGHT and LICENSE for details. The development of repmgr has primarily been sponsored by 2ndQuadrant customers. Additional work has been sponsored by the 4CaaST project for cloud computing, 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`. 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@2ndQuadrant.com for a copy of the relevant Copyright Assignment Form. Code style ---------- Code in repmgr is formatted to a consistent style using the following command: astyle --style=ansi --indent=tab --suffix=none *.c *.h Contributors should reformat their code similarly before submitting code to the project, in order to minimize merge conflicts with other work.repmgr-3.3.1/COPYRIGHT000066400000000000000000000012631306366326400143200ustar00rootroot00000000000000Copyright (c) 2010-2017, 2ndQuadrant Limited All rights reserved. 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/ to obtain one. repmgr-3.3.1/CREDITS000066400000000000000000000011211306366326400140360ustar00rootroot00000000000000Code and documentation contributors to repmgr include: Jaime Casanova Simon Riggs Greg Smith Robert J. Noles Gabriele Bartolini Bas van Oostveen Hannu Krosing Cédric Villemain Charles Duffy Daniel Farina Shawn Ellis Jay Taylor Christian Kruse Krzysztof Gajdemski repmgr-3.3.1/FAILOVER.rst000066400000000000000000000001231306366326400147600ustar00rootroot00000000000000The contents of this file have been incorporated into the main README.md document. repmgr-3.3.1/FAQ.md000066400000000000000000000166231306366326400137640ustar00rootroot00000000000000FAQ - Frequently Asked Questions about repmgr ============================================= This FAQ applies to `repmgr` 3.0 and later. General ------- - What's the difference between the repmgr versions? 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. repmgr 2.x supports PostgreSQL 9.0 onwards. While it is compatible with PostgreSQL 9.3 and later, we recommend repmgr v3. - What's the advantage of using replication slots? Replication slots, introduced in PostgreSQL 9.4, ensure that the master server will retain WAL files until they have been consumed by all standby servers. This makes WAL file management much easier, and if used `repmgr` will no longer insist on a fixed number (default: 5000) of WAL files being preserved. (However this does mean that if a standby is no longer connected to the master, the master will retain WAL files indefinitely). - How many replication slots should I define in `max_replication_slots`? Normally at least same number as the number of standbys which will connect to the node. Note that changes to `max_replication_slots` 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. - Does `repmgr` support hash indexes? No. Hash indexes and replication do not mix well and their use is explicitly discouraged; see: https://www.postgresql.org/docs/current/interactive/sql-createindex.html#AEN74175 `repmgr` -------- - When should I use the --rsync-only option? By default, `repmgr` uses `pg_basebackup` to clone a standby from a master. However, `pg_basebackup` copies the entire data directory, which can take some time depending on installation size. If you have an existing but "stale" standby, `repmgr` can use `rsync` instead, which means only changed or added files need to be copied. - Can I register an existing master/standby? Yes, this is no problem. - How can a failed master be re-added as a standby? This is a two-stage process. First, the failed master's data directory must be re-synced with the current master; secondly the failed master needs to be re-registered as a standby. The section "Converting a failed master to a standby" in the `README.md` file contains more detailed information on this process. - Is there an easy way to check my master server is correctly configured for use with `repmgr`? Yes - execute `repmgr` with the `--check-upstream-config` option, and it will let you know which items in `postgresql.conf` need to be modified. - Even though I specified custom `rsync` options, `repmgr` appends the `--checksum` - why? When syncing a stale data directory from an active server, it's essential that `rsync` compares the content of files rather than just timestamp and size, to ensure that all changed files are copied and prevent corruption. - When cloning a standby, how can I prevent `repmgr` from copying `postgresql.conf` and `pg_hba.conf` from the PostgreSQL configuration directory in `/etc`? Use the command line option `--ignore-external-config-files` - How can I prevent `repmgr` from copying local configuration files in the data directory? If you're updating an existing but stale data directory which contains e.g. configuration files you don't want to be overwritten with the same file from the master, specify the files in the `rsync_options` configuration option, e.g. rsync_options=--exclude=postgresql.local.conf This option is only available when using the `--rsync-only` option. - How can I make the witness server use a particular port? By default the witness server is configured to use port 5499; this is intended to support running the witness server as a separate instance on a normal node server, rather than on its own dedicated server. To specify different port for the witness server, supply the port number in the `conninfo` string in `repmgr.conf` (repmgr 3.0.1 and earlier: use the `-l/--local-port` option) - Do I need to include `shared_preload_libraries = 'repmgr_funcs'` in `postgresql.conf` if I'm not using `repmgrd`? No, the `repmgr_funcs` library is only needed when running `repmgrd`. If you later decide to run `repmgrd`, you just need to add `shared_preload_libraries = 'repmgr_funcs'` and restart PostgreSQL. - I've provided replication permission for the `repmgr` user in `pg_hba.conf` but `repmgr`/`repmgrd` complains it can't connect to the server... Why? `repmgr`/`repmgrd` need to be able to connect to the repmgr database with a normal connection to query metadata. The `replication` connection permission is for PostgreSQL's streaming replication and doesn't necessarily need to be the `repmgr` user. - 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? 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 `repl_nodes` table or if necessary scan the replication cluster until it locates the active primary. - Why is there no foreign key on the `node_id` column in the `repl_events` table? 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 `repl_nodes` table. `repmgrd` --------- - Do I need a witness server? Not necessarily. However if you have an uneven number of nodes spread over more than one network segment, a witness server will enable better handling of a 'split brain' situation by providing a "casting vote" on the preferred network segment. - How can I prevent a node from ever being promoted to master? In `repmgr.conf`, set its priority to a value of 0 or less. Additionally, if `failover` is set to `manual`, the node will never be considered as a promotion candidate. - Does `repmgrd` support delayed standbys? `repmgrd` can monitor delayed standbys - those set up with `recovery_min_apply_delay` set to a non-zero value in `recovery.conf` - but as it's not currently possible to directly examine the value applied to the standby, `repmgrd` may not be able to properly evaluate the node as a promotion candidate. We recommend that delayed standbys are explicitly excluded from promotion by setting `priority` to 0 in `repmgr.conf`. Note that after registering a delayed standby, `repmgrd` will only start once the metadata added in the master node has been replicated. - How can I get `repmgrd` to rotate its logfile? Configure your system's `logrotate` service to do this; see example in README.md - I've recloned a failed master as a standby, but `repmgrd` refuses to start? Check you registered the standby after recloning. If unregistered the standby cannot be considered as a promotion candidate even if `failover` is set to `automatic`, which is probably not what you want. `repmgrd` will start if `failover` is set to `manual` so the node's replication status can still be monitored, if desired. repmgr-3.3.1/HISTORY000066400000000000000000000335051306366326400141150ustar00rootroot000000000000003.3.1 2017-03- repmgrd: prevent invalid apply lag value being written to the monitoring table (Ian) repmgrd: fix error in XLogRecPtr conversion when calculating monitoring statistics (Ian) repmgr: if replication slots in use, where possible delete slot on old upstream node after following new upstream (Ian) repmgr: improve logging of rsync actions (Ian) repmgr: improve `standby clone` when synchronous replication in use (Ian) repmgr: stricter checking of allowed node id values repmgr: enable `master register --force` when there is a foreign key dependency from a standby node (Ian) 3.3 2016-12-27 repmgr: always log to STDERR even if log facility defined (Ian) repmgr: add --log-to-file to log repmgr output to the defined log facility (Ian) repmgr: improve handling of command line parameter errors (Ian) repmgr: add option --upstream-conninfo to explicitly set 'primary_conninfo' in recovery.conf (Ian) repmgr: enable a standby to be registered which isn't running (Ian) repmgr: enable `standby register --force` to update a node record with cascaded downstream node records (Ian) repmgr: add option `--no-conninfo-password` (Abhijit, Ian) repmgr: add initial support for PostgreSQL 10.0 (Ian) repmgr: escape values in primary_conninfo if needed (Ian) 3.2.1 2016-10-24 repmgr: require a valid repmgr cluster name unless -F/--force supplied (Ian) repmgr: check master server is registered with repmgr before cloning (Ian) repmgr: ensure data directory defaults to that of the source node (Ian) repmgr: various fixes to Barman cloning mode (Gianni, Ian) repmgr: fix `repmgr cluster crosscheck` output (Ian) 3.2 2016-10-05 repmgr: add support for cloning from a Barman backup (Gianni) repmgr: add commands `standby matrix` and `standby crosscheck` (Gianni) repmgr: suppress connection error display in `repmgr cluster show` unless `--verbose` supplied (Ian) repmgr: add commands `witness register` and `witness unregister` (Ian) repmgr: enable `standby unregister` / `witness unregister` to be executed for a node which is not running (Ian) repmgr: remove deprecated command line options --initdb-no-pwprompt and -l/--local-port (Ian) repmgr: before cloning with pg_basebackup, check that sufficient free walsenders are available (Ian) repmgr: add option `--wait-sync` for `standby register` which causes repmgr to wait for the registered node record to synchronise to the standby (Ian) repmgr: add option `--copy-external-config-files` for files outside of the data directory (Ian) repmgr: only require `wal_keep_segments` to be set in certain corner cases (Ian) repmgr: better support cloning from a node other than the one to stream from (Ian) repmgrd: add configuration options to override the default pg_ctl commands (Jarkko Oranen, Ian) repmgrd: don't start if node is inactive and failover=automatic (Ian) packaging: improve "repmgr-auto" Debian package (Gianni) 3.1.5 2016-08-15 repmgrd: in a failover situation, prevent endless looping when attempting to establish the status of a node with `failover=manual` (Ian) repmgrd: improve handling of failover events on standbys with `failover=manual`, and create a new event notification for this, `standby_disconnect_manual` (Ian) repmgr: add further event notifications (Gianni) repmgr: when executing `standby switchover`, don't collect remote command output unless required (Gianni, Ian) repmgrd: improve standby monitoring query (Ian, based on suggestion from Álvaro) repmgr: various command line handling improvements (Ian) 3.1.4 2016-07-12 repmgr: new configuration option for setting "restore_command" in the recovery.conf file generated by repmgr (Martín) repmgr: add --csv option to "repmgr cluster show" (Gianni) repmgr: enable provision of a conninfo string as the -d/--dbname parameter, similar to other PostgreSQL utilities (Ian) repmgr: during switchover operations improve detection of demotion candidate shutdown (Ian) various bugfixes and documentation updates (Ian, Martín) 3.1.3 2016-05-17 repmgrd: enable monitoring when a standby is catching up by replaying archived WAL (Ian) repmgrd: when upstream_node_id is NULL, assume upstream node to be current master (Ian) repmgrd: check for reappearance of the master node if standby promotion fails (Ian) improve handling of rsync failure conditions (Martín) 3.1.2 2016-04-12 Fix pg_ctl path generation in do_standby_switchover() (Ian) Regularly sync witness server repl_nodes table (Ian) Documentation improvements (Gianni, dhyannataraj) (Experimental) ensure repmgr handles failover slots when copying in rsync mode (Craig, Ian) rsync mode handling fixes (Martín) Enable repmgr to compile against 9.6devel (Ian) 3.1.1 2016-02-24 Add '-P/--pwprompt' option for "repmgr create witness" (Ian) Prevent repmgr/repmgrd running as root (Ian) 3.1.0 2016-02-01 Add "repmgr standby switchover" command (Ian) Revised README file (Ian) Remove requirement for 'archive_mode' to be enabled (Ian) Improve -?/--help output, showing default values if relevant (Ian) Various bugfixes to command line/configuration parameter handling (Ian) 3.0.3 2016-01-04 Create replication slot if required before base backup is run (Abhijit) standy clone: when using rsync, clean up "pg_replslot" directory (Ian) Improve --help output (Ian) Improve config file parsing (Ian) Various logging output improvements, including explicit HINTS (Ian) Add --log-level to explicitly set log level on command line (Ian) Repurpose --verbose to display extra log output (Ian) Add --terse to hide hints and other non-critical output (Ian) Reference internal functions with explicit catalog path (Ian) When following a new primary, have repmgr (not repmgrd) create the new slot (Ian) Add /etc/repmgr.conf as a default configuration file location (Ian) Prevent repmgrd's -v/--verbose option expecting a parameter (Ian) Prevent invalid replication_lag values being written to the monitoring table (Ian) Improve repmgrd behaviour when monitored standby node is temporarily unavailable (Martín) 3.0.2 2015-10-02 Improve handling of --help/--version options; and improve help output (Ian) Improve handling of situation where logfile can't be opened (Ian) Always pass -D/--pgdata option to pg_basebackup (Ian) Bugfix: standby clone --force does not empty pg_xlog (Gianni) Bugfix: autofailover with reconnect_attempts > 1 (Gianni) Bugfix: ignore comments after values (soxwellfb) Bugfix: handle string values in 'node' parameter correctly (Gregory Duchatelet) Allow repmgr to be compiled with a newer libpq (Marco) Bugfix: call update_node_record_set_upstream() for STANDBY FOLLOW (Tomas) Update `repmgr --help` output (per Github report from renard) Update tablespace remapping in --rsync-only mode for 9.5 and later (Ian) Deprecate `-l/--local-port` option - the port can be extracted from the conninfo string in repmgr.conf (Ian) Add STANDBY UNREGISTER (Vik Fearing) Don't fail with error when registering master if schema already defined (Ian) Fixes to whitespace handling when parsing config file (Ian) 3.0.1 2015-04-16 Prevent repmgrd from looping infinitely if node was not registered (Ian) When promoting a standby, have repmgr (not repmgrd) handle metadata updates (Ian) Re-use replication slot if it already exists (Ian) Prevent a test SSH connection being made when not needed (Ian) Correct monitoring table column names (Ian) 3.0 2015-03-27 Require PostgreSQL 9.3 or later (Ian) Use `pg_basebackup` by default (instead of `rsync`) to clone standby servers (Ian) Use `pg_ctl promote` to promote a standby to primary Enable tablespace remapping using `pg_basebackup` (in PostgreSQL 9.3 with `rsync`) (Ian) Support cascaded standbys (Ian) "pg_bindir" no longer required as a configuration parameter (Ian) Enable replication slots to be used (PostgreSQL 9.4 and later (Ian) Command line option "--check-upstream-config" (Ian) Add event logging table and option to execute an external program when an event occurs (Ian) General usability and logging message improvements (Ian) Code consolidation and cleanup (Ian) 2.0.3 2015-04-16 Add -S/--superuser option for witness database creation Ian) Add -c/--fast-checkpoint option for cloning (Christoph) Add option "--initdb-no-pwprompt" (Ian) 2.0.2 2015-02-17 Add "--checksum" in rsync when using "--force" (Jaime) Use createdb/createuser instead of psql (Jaime) Fixes to witness creation and monitoring (wamonite) Use default master port if none supplied (Martín) Documentation fixes and improvements (Ian) 2.0.1 2014-07-16 Documentation fixes and new QUICKSTART file (Ian) Explicitly specify directories to ignore when cloning (Ian) Fix log level for some log messages (Ian) RHEL/CentOS specfile, init script and Makefile fixes (Nathan Van Overloop) Debian init script and config file documentation fixes (József Kószó) Typo fixes (Riegie Godwin Jeyaranchen, PriceChild) 2.0stable 2014-01-30 Documentation fixes (Christian) General refactoring, code quality improvements and stabilization work (Christian) Added proper daemonizing (-d/--daemonize) (Christian) Added PID file handling (-p/--pid-file) (Christian) New config option: monitor_interval_secs (Christian) New config option: retry_promote_interval (Christian) New config option: logfile (Christian) New config option: pg_bindir (Christian) New config option: pgctl_options (Christian) 2.0beta2 2013-12-19 Improve autofailover logic and algorithms (Jaime, Andres) Ignore pg_log when cloning (Jaime) Add timestamps to log line in stderr (Christian) Correctly check wal_keep_segments (Jay Taylor) Add a ssh_options parameter (Jay Taylor) 2.0beta1 2012-07-27 Make CLONE command try to make an exact copy including $PGDATA location (Cedric) Add detection of master failure (Jaime) Add the notion of a witness server (Jaime) Add autofailover capabilities (Jaime) Add a configuration parameter to indicate the script to execute on failover or follow (Jaime) Make the monitoring optional and turned off by default, it can be turned on with --monitoring-history switch (Jaime) Add tunables to specify number of retries to reconnect to master and the time between them (Jaime) 1.2.0 2012-07-27 Test ssh connection before trying to rsync (Cédric) Add CLUSTER SHOW command (Carlo) Add CLUSTER CLEANUP command (Jaime) Add function write_primary_conninfo (Marco) Teach repmgr how to get tablespace's location in different pg version (Jaime) Improve version message (Carlo) 1.1.1 2012-04-18 Add --ignore-rsync-warning (Cédric) Add strnlen for compatibility with OS X (Greg) Improve performance of the repl_status view (Jaime) Remove last argument from log_err (Jaime, Reported by Jeroen Dekkers) Complete documentation about possible error conditions (Jaime) Document how to clean history (Jaime) 1.1.0 2011-03-09 Make options -U, -R and -p not mandatory (Jaime) 1.1.0b1 2011-02-24 Fix missing "--force" option in help (Greg Smith) Correct warning message for wal_keep_segments (Bas van Oostveen) Add Debian build/usage docs (Bas, Hannu Krosing, Cedric Villemain) Add Debian .deb packaging (Hannu) Move configuration data into a structure (Bas, Gabriele Bartolini) Make rsync options configurable (Bas) Add syslog as alternate logging destination (Gabriele) Change from using malloc to static memory allocations (Gabriele) Add debugging messages after every query (Gabriele) Parameterize schema name used for repmgr (Gabriele) Avoid buffer overruns by using snprintf etc. (Gabriele) Fix use of database query after close (Gabriele) Add information about progress during "standby clone" (Gabriele) Fix double free errors in repmgrd (Charles Duffy, Greg) Make repmgr exit with an error code when encountering an error (Charles) Standardize on error return codes, use in repmgrd too (Greg) Add [un]install actions/SQL like most contrib modules (Daniel Farina) Wrap all string construction and produce error on overflow (Daniel) Correct freeing of memory from first_wal_segment (Daniel) Allow creating recovery.conf file with a password (Daniel) Inform when STANDBY CLONE sees an unused config file (Daniel) Use 64-bit computation for WAL apply_lag (Greg) Add info messages for database and general work done (Greg) Map old verbose flag into a useful setting for the new logger (Greg) Document repmgrd startup restrictions and log info about them (Greg) 1.0.0 2010-12-05 First public release repmgr-3.3.1/LICENSE000066400000000000000000001045141306366326400140350ustar00rootroot00000000000000 GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) 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 . Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: Copyright (C) This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see . The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read . repmgr-3.3.1/Makefile000066400000000000000000000064111306366326400144650ustar00rootroot00000000000000# # Makefile # Copyright (c) 2ndQuadrant, 2010-2017 HEADERS = $(wildcard *.h) repmgrd_OBJS = dbutils.o config.o repmgrd.o log.o strutil.o repmgr_OBJS = dbutils.o check_dir.o config.o repmgr.o log.o strutil.o dirmod.o compat.o DATA = repmgr.sql uninstall_repmgr.sql PG_CPPFLAGS = -I$(libpq_srcdir) PG_LIBS = $(libpq_pgport) all: repmgrd repmgr $(MAKE) -C sql repmgrd: $(repmgrd_OBJS) $(CC) -o repmgrd $(CFLAGS) $(repmgrd_OBJS) $(PG_LIBS) $(LDFLAGS) $(LDFLAGS_EX) $(LIBS) $(MAKE) -C sql repmgr: $(repmgr_OBJS) $(CC) -o repmgr $(CFLAGS) $(repmgr_OBJS) $(PG_LIBS) $(LDFLAGS) $(LDFLAGS_EX) $(LIBS) # Make all objects depend on all include files. This is a bit of a # shotgun approach, but the codebase is small enough that a complete rebuild # is very fast anyway. $(repmgr_OBJS): $(HEADERS) $(repmgrd_OBJS): $(HEADERS) ifdef USE_PGXS PG_CONFIG = pg_config PGXS := $(shell $(PG_CONFIG) --pgxs) include $(PGXS) else subdir = contrib/repmgr top_builddir = ../.. include $(top_builddir)/src/Makefile.global include $(top_srcdir)/contrib/contrib-global.mk endif # XXX: This overrides the pgxs install target - we're building two binaries, # which is not supported by pgxs.mk's PROGRAM construct. install: install_prog install_ext install_prog: mkdir -p '$(DESTDIR)$(bindir)' $(INSTALL_PROGRAM) repmgrd$(X) '$(DESTDIR)$(bindir)/' $(INSTALL_PROGRAM) repmgr$(X) '$(DESTDIR)$(bindir)/' install_ext: $(MAKE) -C sql install # Distribution-specific package building targets # ---------------------------------------------- # # XXX we recommend using the PGDG-supplied packages where possible; # see README.md for details. install_rhel: mkdir -p '$(DESTDIR)/etc/init.d/' $(INSTALL_PROGRAM) RHEL/repmgrd.init '$(DESTDIR)/etc/init.d/repmgrd' mkdir -p '$(DESTDIR)/etc/sysconfig/' $(INSTALL_PROGRAM) RHEL/repmgrd.sysconfig '$(DESTDIR)/etc/sysconfig/repmgrd' mkdir -p '$(DESTDIR)/etc/repmgr/' $(INSTALL_PROGRAM) repmgr.conf.sample '$(DESTDIR)/etc/repmgr/' mkdir -p '$(DESTDIR)/usr/bin/' $(INSTALL_PROGRAM) repmgrd$(X) '$(DESTDIR)/usr/bin/' $(INSTALL_PROGRAM) repmgr$(X) '$(DESTDIR)/usr/bin/' ifneq (,$(DATA)$(DATA_built)) @for file in $(addprefix $(srcdir)/, $(DATA)) $(DATA_built); do \ echo "$(INSTALL_DATA) $$file '$(DESTDIR)$(datadir)/$(datamoduledir)'"; \ $(INSTALL_DATA) $$file '$(DESTDIR)$(datadir)/$(datamoduledir)'; \ done endif clean: rm -f *.o rm -f repmgrd rm -f repmgr $(MAKE) -C sql clean # Get correct version numbers and install paths, depending on your postgres version PG_VERSION = $(shell pg_config --version | cut -d ' ' -f 2 | cut -d '.' -f 1,2) REPMGR_VERSION = $(shell grep REPMGR_VERSION version.h | cut -d ' ' -f 3 | cut -d '"' -f 2) PKGLIBDIR = $(shell pg_config --pkglibdir) SHAREDIR = $(shell pg_config --sharedir) PGBINDIR = /usr/lib/postgresql/$(PG_VERSION)/bin deb: repmgrd repmgr mkdir -p ./debian/usr/bin ./debian$(PGBINDIR) cp repmgrd repmgr ./debian$(PGBINDIR) ln -s ../..$(PGBINDIR)/repmgr ./debian/usr/bin/repmgr mkdir -p ./debian$(SHAREDIR)/contrib/ cp sql/repmgr_funcs.sql ./debian$(SHAREDIR)/contrib/ cp sql/uninstall_repmgr_funcs.sql ./debian$(SHAREDIR)/contrib/ mkdir -p ./debian$(PKGLIBDIR)/ cp sql/repmgr_funcs.so ./debian$(PKGLIBDIR)/ dpkg-deb --build debian mv debian.deb ../postgresql-repmgr-$(PG_VERSION)_$(REPMGR_VERSION).deb rm -rf ./debian/usr repmgr-3.3.1/PACKAGES.md000066400000000000000000000120271306366326400145250ustar00rootroot00000000000000Packaging ========= Notes on RedHat Linux, Fedora, and CentOS Builds ------------------------------------------------ The RPM packages of PostgreSQL put `pg_config` into the `postgresql-devel` package, not the main server one. And if you have a RPM install of PostgreSQL 9.0, the entire PostgreSQL binary directory will not be in your PATH by default either. Individual utilities are made available via the `alternatives` mechanism, but not all commands will be wrapped that way. The files installed by repmgr will certainly not be in the default PATH for the postgres user on such a system. They will instead be in /usr/pgsql-9.0/bin/ on this type of system. When building repmgr against a RPM packaged build, you may discover that some development packages are needed as well. The following build errors can occur: /usr/bin/ld: cannot find -lxslt /usr/bin/ld: cannot find -lpam Install the following packages to correct those: yum install libxslt-devel yum install pam-devel If building repmgr as a regular user, then doing the install into the system directories using sudo, the syntax is hard. `pg_config` won't be in root's path either. The following recipe should work: sudo PATH="/usr/pgsql-9.0/bin:$PATH" make USE_PGXS=1 install Issues with 32 and 64 bit RPMs ------------------------------ If when building, you receive a series of errors of this form: /usr/bin/ld: skipping incompatible /usr/pgsql-9.0/lib/libpq.so when searching for -lpq This is likely because you have both the 32 and 64 bit versions of the `postgresql90-devel` package installed. You can check that like this: rpm -qa --queryformat '%{NAME}\t%{ARCH}\n' | grep postgresql90-devel And if two packages appear, one for i386 and one for x86_64, that's not supposed to be allowed. This can happen when using the PGDG repo to install that package; here is an example sessions demonstrating the problem case appearing: # yum install postgresql-devel .. Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package postgresql90-devel.i386 0:9.0.2-2PGDG.rhel5 set to be updated ---> Package postgresql90-devel.x86_64 0:9.0.2-2PGDG.rhel5 set to be updated --> Finished Dependency Resolution Dependencies Resolved ========================================================================= Package Arch Version Repository Size ========================================================================= Installing: postgresql90-devel i386 9.0.2-2PGDG.rhel5 pgdg90 1.5 M postgresql90-devel x86_64 9.0.2-2PGDG.rhel5 pgdg90 1.6 M Note how both the i386 and x86_64 platform architectures are selected for installation. Your main PostgreSQL package will only be compatible with one of those, and if the repmgr build finds the wrong postgresql90-devel these "skipping incompatible" messages appear. In this case, you can temporarily remove both packages, then just install the correct one for your architecture. Example: rpm -e postgresql90-devel --allmatches yum install postgresql90-devel-9.0.2-2PGDG.rhel5.x86_64 Instead just deleting the package from the wrong platform might not leave behind the correct files, due to the way in which these accidentally happen to interact. If you already tried to build repmgr before doing this, you'll need to do: make USE_PGXS=1 clean to get rid of leftover files from the wrong architecture. Notes on Ubuntu, Debian or other Debian-based Builds ---------------------------------------------------- The Debian packages of PostgreSQL put `pg_config` into the development package called `postgresql-server-dev-$version`. When building repmgr against a Debian packages build, you may discover that some development packages are needed as well. You will need the following development packages installed: sudo apt-get install libxslt-dev libxml2-dev libpam-dev libedit-dev If you're using Debian packages for PostgreSQL and are building repmgr with the USE_PGXS option you also need to install the corresponding development package: sudo apt-get install postgresql-server-dev-9.0 If you build and install repmgr manually it will not be on the system path. The binaries will be installed in /usr/lib/postgresql/$version/bin/ which is not on the default path. The reason behind this is that Ubuntu/Debian systems manage multiple installed versions of PostgreSQL on the same system through a wrapper called pg_wrapper and repmgr is not (yet) known to this wrapper. You can solve this in many different ways, the most Debian like is to make an alternate for repmgr and repmgrd: sudo update-alternatives --install /usr/bin/repmgr repmgr /usr/lib/postgresql/9.0/bin/repmgr 10 sudo update-alternatives --install /usr/bin/repmgrd repmgrd /usr/lib/postgresql/9.0/bin/repmgrd 10 You can also make a deb package of repmgr using: make USE_PGXS=1 deb This will build a Debian package one level up from where you build, normally the same directory that you have your repmgr/ directory in. repmgr-3.3.1/QUICKSTART.md000066400000000000000000000001231306366326400150330ustar00rootroot00000000000000The contents of this file have been incorporated into the main README.md document. repmgr-3.3.1/README.md000066400000000000000000002427651306366326400143220ustar00rootroot00000000000000repmgr: Replication Manager for PostgreSQL ========================================== `repmgr` is a suite of open-source tools to manage replication and failover within a cluster of PostgreSQL servers. It enhances PostgreSQL's built-in replication capabilities with utilities to set up standby servers, monitor replication, and perform administrative tasks such as failover or switchover operations. The current `repmgr` version (3.3) supports all PostgreSQL versions from 9.3 to 9.6. Overview -------- The `repmgr` suite provides two main tools: - `repmgr` - a command-line tool used to perform administrative tasks such as: - setting up standby servers - promoting a standby server to master - switching over master and standby servers - displaying the status of servers in the replication cluster - `repmgrd` is a daemon which actively monitors servers in a replication cluster and performs the following tasks: - monitoring and recording replication performance - performing failover by detecting failure of the master and promoting the most suitable standby server - provide notifications about events in the cluster to a user-defined script which can perform tasks such as sending alerts by email `repmgr` supports and enhances PostgreSQL's built-in streaming replication, which provides a single read/write master server and one or more read-only standbys containing near-real time copies of the master server's database. For a multi-master replication solution, please see 2ndQuadrant's BDR (bi-directional replication) extension. http://2ndquadrant.com/en-us/resources/bdr/ For selective replication, e.g. of individual tables or databases from one server to another, please see 2ndQuadrant's pglogical extension. http://2ndquadrant.com/en-us/resources/pglogical/ ### Concepts This guide assumes that you are familiar with PostgreSQL administration and streaming replication concepts. For further details on streaming replication, see this link: https://www.postgresql.org/docs/current/interactive/warm-standby.html#STREAMING-REPLICATION The following terms are used throughout the `repmgr` documentation. - `replication cluster` In the `repmgr` documentation, "replication cluster" refers to the network of PostgreSQL servers connected by streaming replication. - `node` A `node` is a server within a replication cluster. - `upstream node` This is the node a standby server is connected to; either the master server or in the case of cascading replication, another standby. - `failover` This is the action which occurs if a master server fails and a suitable standby is promoted as the new master. The `repmgrd` daemon supports automatic failover to minimise downtime. - `switchover` In certain circumstances, such as hardware or operating system maintenance, it's necessary to take a master server offline; in this case a controlled switchover is necessary, whereby a suitable standby is promoted and the existing master removed from the replication cluster in a controlled manner. The `repmgr` command line client provides this functionality. - `witness server` `repmgr` provides functionality to set up a so-called "witness server" to assist in determining a new master 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 (see below). 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 master; this is to prevent a "split-brain" situation where an isolated location interprets a network outage as a failure of the (remote) master and promotes a (local) standby. A witness server only needs to be created if `repmgrd` is in use. ### repmgr user and metadata 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 during the first step in initialising a `repmgr`-controlled cluster (`repmgr master register`) and contains the following objects: tables: - `repl_events`: records events of interest - `repl_nodes`: connection and status information for each server in the replication cluster - `repl_monitor`: historical standby monitoring information written by `repmgrd` views: - `repl_show_nodes`: based on the table `repl_nodes`, additionally showing the name of the server's upstream node - `repl_status`: when `repmgrd`'s monitoring is enabled, shows current monitoring status for each node 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`. A dedicated database superuser is required to own the meta-database as well as carry out administrative actions. Installation ------------ ### System requirements `repmgr` is developed and tested on Linux and OS X, but should work on any UNIX-like system supported by PostgreSQL itself. Current versions of `repmgr` support PostgreSQL from version 9.3. If you are interested in using `repmgr` on earlier versions of PostgreSQL you can download version 2.1 which supports PostgreSQL from version 9.1. 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. The `repmgr` tools must be installed on each server in the replication cluster. A dedicated system user for `repmgr` is *not* required; as many `repmgr` and `repmgrd` actions require direct access to the PostgreSQL data directory, these commands should be executed by the `postgres` user. Passwordless `ssh` connectivity between all servers in the replication cluster is not required, but is necessary in the following cases: * if you need `repmgr` to copy configuration files from outside the PostgreSQL data directory * when using `rsync` to clone a standby * to perform switchover operations * when executing `repmgr cluster matrix` and `repmgr cluster crosscheck` In these cases `rsync` is required on all servers too. * * * > *TIP*: We recommend using a session multiplexer utility such as `screen` or > `tmux` 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 `ssh` session to the server is interrupted or closed. * * * ### Packages We recommend installing `repmgr` using the available packages for your system. - RedHat/CentOS: RPM packages for `repmgr` are available via Yum through the PostgreSQL Global Development Group RPM repository ( http://yum.postgresql.org/ ). Follow the instructions for your distribution (RedHat, CentOS, Fedora, etc.) and architecture as detailed at yum.postgresql.org. 2ndQuadrant also provides its own RPM packages which are made available at the same time as each `repmgr` release, as it can take some days for them to become available via the main PGDG repository. See here for details: http://repmgr.org/yum-repository.html - Debian/Ubuntu: the most recent `repmgr` packages are available from the PostgreSQL Community APT repository ( http://apt.postgresql.org/ ). Instructions can be found in the APT section of the PostgreSQL Wiki ( https://wiki.postgresql.org/wiki/Apt ). See `PACKAGES.md` for details on building .deb and .rpm packages from the `repmgr` source code. ### Source installation `repmgr` source code can be obtained directly from the project GitHub repository: git clone https://github.com/2ndQuadrant/repmgr Release tarballs are also available: https://github.com/2ndQuadrant/repmgr/releases http://repmgr.org/downloads.php `repmgr` is compiled in the same way as a PostgreSQL extension using the PGXS infrastructure, e.g.: sudo make USE_PGXS=1 install `repmgr` can be built from source in any environment suitable for building PostgreSQL itself. ### Configuration `repmgr` and `repmgrd` use a common configuration file, by default called `repmgr.conf` (although any name can be used if explicitly specified). At the very least, `repmgr.conf` must contain the connection parameters for the local `repmgr` database; see `repmgr configuration file` below for more details. The configuration file will be searched for in the following locations: - a configuration file specified by the `-f/--config-file` command line option - `repmgr.conf` in the local directory - `/etc/repmgr.conf` - the directory reported by `pg_config --sysconfdir` Note that if a file is explicitly specified with `-f/--config-file`, 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 `repmgr` unexpectedly reading the wrong file. For a full list of annotated configuration items, see the file `repmgr.conf.sample`. The following parameters in the configuration file can be overridden with command line options: - `log_level` with `-L/--log-level` - `pg_bindir` with `-b/--pg_bindir` ### Logging By default `repmgr` and `repmgrd` will log directly to `STDERR`. For `repmgrd` we recommend capturing output in a logfile or using your system's log facility; see `repmgr.conf.sample` for details. As a command line utility, `repmgr` will log directly to the console by default (this is a change in behaviour from versions before 3.3, where it would always log to the same location as `repmgrd`). However in some circumstances, such as when `repmgr` is executed by `repmgrd` during a failover event, it makes sense to capture `repmgr`'s log output - this can be done by supplying the command-line option `--log-to-file` to `repmgr`. ### Command line options and environment variables For some commands, e.g. `repmgr standby clone`, database connection parameters need to be provided. Like other PostgreSQL utilities, following standard parameters can be used: - `-d/--dbname=DBNAME` - `-h/--host=HOSTNAME` - `-p/--port=PORT` - `-U/--username=USERNAME` If `-d/--dbname` contains an `=` sign or starts with a valid URI prefix (`postgresql://` or `postgres://`), it is treated as a conninfo string. See the PostgreSQL documentation for further details: https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNSTRING Note that if a `conninfo` string is provided, values set in this will override any provided as individual parameters. For example, with `-d 'host=foo' --host bar`, `foo` will be chosen over `bar`. Like other PostgreSQL utilities, `repmgr` will default to any values set in environment variables if explicit command line parameters are not provided. See the PostgreSQL documentation for further details: https://www.postgresql.org/docs/current/static/libpq-envars.html Setting up a simple replication cluster with repmgr --------------------------------------------------- The following section will describe how to set up a basic replication cluster with a master and a standby server using the `repmgr` command line tool. It is assumed PostgreSQL is installed on both servers in the cluster, `rsync` is available and passwordless SSH connections are possible between both servers. * * * > *TIP*: for testing `repmgr`, it's possible to use multiple PostgreSQL > instances running on different ports on the same computer, with > passwordless SSH access to `localhost` enabled. * * * ### PostgreSQL configuration On the master server, a PostgreSQL instance must be initialised and running. The following replication settings may need to be adjusted: # Enable replication connections; set this figure 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) max_wal_senders = 10 # Ensure WAL files contain enough information to enable read-only queries # on the standby wal_level = 'hot_standby' # Enable read-only queries on a standby # (Note: this will be ignored on a master but we recommend including # it anyway) hot_standby = on # Enable WAL file archiving archive_mode = on # Set archive command to a script or application that will safely store # you WALs in a secure place. /bin/true is an example of a command that # ignores archiving. Use something more sensible. archive_command = '/bin/true' # If cloning using rsync, or you have configured `pg_basebackup_options` # in `repmgr.conf` to include the setting `--xlog-method=fetch` (from # PostgreSQL 10 `--wal-method=fetch`), *and* you have not set # `restore_command` in `repmgr.conf`to fetch WAL files from another # source such as Barman, you'll need to set `wal_keep_segments` to a # high enough value to ensure that all WAL files generated while # the standby is being cloned are retained until the standby starts up. # wal_keep_segments = 5000 * * * > *TIP*: rather than editing these settings in the default `postgresql.conf` > file, create a separate file such as `postgresql.replication.conf` and > include it from the end of the main configuration file with: > `include 'postgresql.replication.conf'` * * * Create a dedicated PostgreSQL superuser account and a database for the `repmgr` metadata, e.g. createuser -s repmgr createdb repmgr -O repmgr For the examples in this document, the name `repmgr` will be used for both user and database, but any names can be used. Ensure the `repmgr` user has appropriate permissions in `pg_hba.conf` and can connect in replication mode; `pg_hba.conf` should contain entries similar to the following: 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 Adjust according to your network environment and authentication requirements. On the standby, do not create a PostgreSQL instance, but do ensure an empty directory is available for the `postgres` system user to create a data directory. ### repmgr configuration file Create a `repmgr.conf` file on the master server. The file must contain at least the following parameters: cluster=test node=1 node_name=node1 conninfo='host=repmgr_node1 user=repmgr dbname=repmgr' - `cluster`: an arbitrary name for the replication cluster; this must be identical on all nodes - `node`: a unique integer identifying the node; note this must be a positive 32 bit signed integer between 1 and 2147483647 - `node_name`: a unique string identifying the node; we recommend a name specific to the server (e.g. 'server_1'); avoid names indicating the current replication role like 'master' or 'standby' as the server's role could change. - `conninfo`: a valid connection string for the `repmgr` database on the *current* server. (On the standby, the database will not yet exist, but `repmgr` needs to know the connection details to complete the setup process). `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 section `Configuration` above for further details about `repmgr.conf`. `repmgr` will create a schema named after the cluster and prefixed with `repmgr_`, e.g. `repmgr_test`; we also recommend that you set the `repmgr` user's search path to include this schema name, e.g. ALTER USER repmgr SET search_path TO repmgr_test, "$user", public; * * * > *TIP*: for Debian-based distributions we recommend explictly setting > `pg_bindir` to the directory where `pg_ctl` and other binaries not in > the standard path are located. For PostgreSQL 9.5 this would be > `/usr/lib/postgresql/9.5/bin/`. * * * ### Initialise the master server To enable `repmgr` to support a replication cluster, the master node must be registered with `repmgr`, which creates the `repmgr` database and adds a metadata record for the server: $ repmgr -f repmgr.conf master register NOTICE: master node correctly registered for cluster test with id 1 (conninfo: host=repmgr_node1 user=repmgr dbname=repmgr) The metadata record looks like this: repmgr=# SELECT * FROM repmgr_test.repl_nodes; id | type | upstream_node_id | cluster | name | conninfo | slot_name | priority | active ----+---------+------------------+---------+-------+---------------------------------------------+-----------+----------+-------- 1 | master | | test | node1 | host=repmgr_node1 dbname=repmgr user=repmgr | | 100 | t (1 row) Each server in the replication cluster will have its own record and will be updated when its status or role changes. ### Clone the standby server Create a `repmgr.conf` file on the standby server. It must contain at least the same parameters as the master's `repmgr.conf`, but with the values `node`, `node_name` and `conninfo` adjusted accordingly, e.g.: cluster=test node=2 node_name=node2 conninfo='host=repmgr_node2 user=repmgr dbname=repmgr' Clone the standby with: $ repmgr -h repmgr_node1 -U repmgr -d repmgr -D /path/to/node2/data/ -f /etc/repmgr.conf standby clone NOTICE: destination directory '/path/to/node2/data/' provided NOTICE: starting backup... HINT: this may take some time; consider using the -c/--fast-checkpoint option NOTICE: pg_stop_backup complete, all required WAL segments have been archived NOTICE: standby clone (using pg_basebackup) complete NOTICE: you can now start your PostgreSQL server HINT: for example : pg_ctl -D /path/to/node2/data/ start This will clone the PostgreSQL data directory files from the master at `repmgr_node1` using PostgreSQL's `pg_basebackup` utility. A `recovery.conf` file containing the correct parameters to start streaming from this master server will be created automatically. Note that by default, any configuration files in the master's data directory will be copied to the standby. Typically these will be `postgresql.conf`, `postgresql.auto.conf`, `pg_hba.conf` and `pg_ident.conf`. These may require modification before the standby is started so it functions as desired. 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 master server. Add the option `--copy-external-config-files` to the `repmgr standby clone` command; by default files will be copied to the same path as on the upstream server. To have them placed in the standby's data directory, specify `--copy-external-config-files=pgdata`, but note that any include directives in the copied files may need to be updated. *Caveat*: when copying external configuration files: `repmgr` will only be able to detect files which contain active settings. If a file is referenced by an include directive but is empty, only contains comments or contains settings which have not been activated, the file will not be copied. * * * > *TIP*: for reliable configuration file management we recommend using a > configuration management tool such as Ansible, Chef, Puppet or Salt. * * * Be aware that 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 `pg_basebackup` method, `repmgr` will set `pg_basebackup`'s `--xlog-method` parameter to `stream`, 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 clonse). To override this behaviour, in `repmgr.conf` set `pg_basebackup`'s `--xlog-method` parameter to `fetch`: pg_basebackup_options='--xlog-method=fetch' and ensure that `wal_keep_segments` is set to an appropriately high value. See the `pg_basebackup` documentation for details: https://www.postgresql.org/docs/current/static/app-pgbasebackup.html > *NOTE*: From PostgreSQL 10, `pg_basebackup`'s `--xlog-method` parameter > has been renamed to `--wal-method`. Make any adjustments to the standby's PostgreSQL configuration files now, then start the server. * * * > *NOTE*: `repmgr standby clone` does not require `repmgr.conf`, however we > recommend providing this as `repmgr` will set the `application_name` parameter > in `recovery.conf` as the value provided in `node_name`, making it easier to > identify the node in `pg_stat_replication`. It's also possible to provide some > advanced options for controlling the standby cloning process; see next section > for details. * * * ### Verify replication is functioning Connect to the master server and execute: repmgr=# SELECT * FROM pg_stat_replication; -[ RECORD 1 ]----+------------------------------ pid | 7704 usesysid | 16384 usename | repmgr application_name | node2 client_addr | 192.168.1.2 client_hostname | client_port | 46196 backend_start | 2016-01-07 17:32:58.322373+09 backend_xmin | state | streaming sent_location | 0/3000220 write_location | 0/3000220 flush_location | 0/3000220 replay_location | 0/3000220 sync_priority | 0 sync_state | async ### Register the standby Register the standby server with: $ repmgr -f /etc/repmgr.conf standby register NOTICE: standby node correctly registered for cluster test with id 2 (conninfo: host=repmgr_node2 user=repmgr dbname=repmgr) Connect to the standby server's `repmgr` database and check the `repl_nodes` table: repmgr=# SELECT * FROM repmgr_test.repl_nodes ORDER BY id; id | type | upstream_node_id | cluster | name | conninfo | slot_name | priority | active ----+---------+------------------+---------+-------+---------------------------------------------+-----------+----------+-------- 1 | master | | test | node1 | host=repmgr_node1 dbname=repmgr user=repmgr | | 100 | t 2 | standby | 1 | test | node2 | host=repmgr_node2 dbname=repmgr user=repmgr | | 100 | t (2 rows) The standby server now has a copy of the records for all servers in the replication cluster. Note that the relationship between master and standby is explicitly defined via the `upstream_node_id` value, which shows here that the standby's upstream server is the replication cluster master. While of limited use in a simple master/standby replication cluster, this information is required to effectively manage cascading replication (see below). * * * > *TIP*: depending on your environment and workload, it may take some time for > the standby's node record to propagate from the master 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 - by providing the option > `--wait-sync` to the `repmgr standby register` command, `repmgr` will wait > until the record is synchronised before exiting. An optional timeout (in > seconds) can be added to this option (e.g. `--wait-sync=60`). * * * 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. In this case, by using the `-F/--force` option and providing the connection parameters to the master server, the standby can be registered. Similarly, with cascading replication it may be necessary to register a standby whose upstream node has not yet been registered - in this case, using `-F/--force` will result in the creation of an inactive placeholder record for the upstream node, which will however later need to be registered with the `-F/--force` option too. When used with `standby register`, care should be taken that use of the `-F/--force` option does not result in an incorrectly configured cluster. ### Using Barman to clone a standby `repmgr standby clone` also supports Barman, the Backup and Replication manager (http://www.pgbarman.org/), as a provider of both base backups and WAL files. Barman support provides the following advantages: - the master node does not need to perform a new backup every time a new standby is cloned; - 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 master node; - therefore, `repmgr` does not need to use replication slots, and the master node does not need to set `wal_keep_segments`. > *NOTE*: In view of the above, Barman support is incompatible with > the `use_replication_slots` setting in `repmgr.conf`. In order to enable Barman support for `repmgr standby clone`, you must ensure that: - the name of the server configured in Barman is equal to the `cluster_name` setting in `repmgr.conf`; - the `barman_server` setting in `repmgr.conf` is set to the SSH hostname of the Barman server; - 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 below); - the Barman catalogue includes at least one valid backup for this server. > *NOTE*: Barman support is automatically enabled if `barman_server` > is set. Normally it is a 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 `--without-barman` command > line option. > *NOTE*: 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 `~/.ssh/config` > corresponding to the value of `barman_server` in `repmgr.conf`. See > the "Host" section in `man 5 ssh_config` for more details. `barman-wal-restore` is a Python script provided by the Barman development team as part of the `barman-cli` package (Barman 2.0 and later; for Barman 1.x the script is provided separately as `barman-wal-restore.py`). `restore_command` must then be set in `repmgr.conf` as follows: