diff --git a/doc/repmgr.sgml b/doc/repmgr.sgml index 16cac2b9..d93e1a0a 100644 --- a/doc/repmgr.sgml +++ b/doc/repmgr.sgml @@ -73,7 +73,6 @@ &promoting-standby; &follow-new-primary; &switchover; - &configuring-witness-server; &event-notifications; &upgrading-repmgr; @@ -83,6 +82,7 @@ &repmgrd-overview; &repmgrd-automatic-failover; &repmgrd-configuration; + &configuring-witness-server; &repmgrd-operation; &repmgrd-bdr; diff --git a/doc/repmgrd-configuration.sgml b/doc/repmgrd-configuration.sgml index a429bcae..c37c62db 100644 --- a/doc/repmgrd-configuration.sgml +++ b/doc/repmgrd-configuration.sgml @@ -53,7 +53,7 @@ - + connection_check_type diff --git a/doc/repmgrd-overview.sgml b/doc/repmgrd-overview.sgml index 613b2479..7f67e7a8 100644 --- a/doc/repmgrd-overview.sgml +++ b/doc/repmgrd-overview.sgml @@ -13,6 +13,66 @@ failover and updating standbys to follow the new primary, as well as providing monitoring information about the state of each standby. + + repmgrd is designed to be straightforward to set up + and does not require additional external infrastructure. + + + Functionality provided by repmgrd includes: + + + + + wide range of configuration options + + + + + + option to execute custom scripts ("event notifications + at different points in the failover sequence + + + + + + ability to pause repmgrd + operation on all nodes with a + single command + + + + + + optional witness server + + + + + + "location" configuration option to restrict + potential promotion candidates to a single location + (e.g. when nodes are spread over multiple data centres) + + + + + + choice of method to determine node availability + (PostgreSQL ping, query execution or new connection) + + + + + + retention of monitoring statistics (optional) + + + + + + +