Each repmgr.conf file must contain the following parameters:
A unique integer greater than zero which identifies the node.
An arbitrary (but unique) string; we recommend using the server's hostname or another identifier unambiguously associated with the server to avoid confusion. Avoid choosing names which reflect the node's current role, e.g. primary or standby1 as roles can change and if you end up in a solution where the current primary is called standby1 (for example), things will be confusing to say the least.
Database connection information as a conninfo string. All servers in the cluster must be able to connect to the local node using this string.
For details on conninfo strings, see section Connection Strings in the PosgreSQL documentation.
If repmgrd is in use, consider explicitly setting connect_timeout in the conninfo string to determine the length of time which elapses before a network connection attempt is abandoned; for details see the PostgreSQL documentation.
The node's data directory. This is needed by repmgr when performing operations when the PostgreSQL instance is not running and there's no other way of determining the data directory.
For a full list of annotated configuration items, see the file repmgr.conf.sample.
For repmgrd-specific settings, see Chapter 13.
Note: The following parameters in the configuration file can be overridden with command line options:
-L/--log-level overrides log_level in repmgr.conf
-b/--pg_bindir overrides pg_bindir in repmgr.conf