diff --git a/configfile.c b/configfile.c
index 4e345991..d3fdddb7 100644
--- a/configfile.c
+++ b/configfile.c
@@ -1055,11 +1055,13 @@ parse_time_unit_parameter(const char *name, const char *value, char *dest, ItemL
* - repmgrd_standby_startup_timeout
* - retry_promote_interval_secs
*
- * non-changeable options
+ * non-changeable options (repmgrd references these from the "repmgr.nodes"
+ * table, not the configuration file)
*
* - node_id
* - node_name
* - data_directory
+ * - location
* - priority
* - replication_type
*
@@ -1275,7 +1277,7 @@ reload_config(t_configuration_options *orig_options, t_server_type server_type)
config_changed = true;
}
- /* promote_delay */
+ /* promote_delay (for testing use only; not documented */
if (orig_options->promote_delay != new_options.promote_delay)
{
orig_options->promote_delay = new_options.promote_delay;
diff --git a/doc/repmgrd-configuration.sgml b/doc/repmgrd-configuration.sgml
index e14a904c..252a2115 100644
--- a/doc/repmgrd-configuration.sgml
+++ b/doc/repmgrd-configuration.sgml
@@ -34,24 +34,6 @@
the PostgreSQL documentation.
-
- To apply configuration file changes to a running repmgrd
- daemon, execute the operating system's rrepmgrd service reload command
- (see for examples),
- or for instances which were manually started, execute kill -HUP, e.g.
- kill -HUP `cat /tmp/repmgrd.pid`.
-
-
-
- Check the repmgrd log to see what changes were
- applied, or if any issues were encountered when reloading the configuration.
-
-
-
- Note that only a subset of configuration file parameters can be changed on a
- running repmgrd daemon.
-
-
automatic failover configuration
@@ -167,6 +149,203 @@
+
+
+ repmgrd
+ applying configuration changes
+
+ Applying configuration changes to repmgrd
+
+ To apply configuration file changes to a running repmgrd
+ daemon, execute the operating system's repmgrd service reload command
+ (see for examples),
+ or for instances which were manually started, execute kill -HUP, e.g.
+ kill -HUP `cat /tmp/repmgrd.pid`.
+
+
+
+ Check the repmgrd log to see what changes were
+ applied, or if any issues were encountered when reloading the configuration.
+
+
+
+ Note that only the following subset of configuration file parameters can be changed on a
+ running repmgrd daemon:
+
+
+
+
+
+ async_query_timeout
+
+
+
+
+
+ bdr_local_monitoring_only
+
+
+
+
+
+ bdr_recovery_timeout
+
+
+
+
+
+ conninfo
+
+
+
+
+
+ degraded_monitoring_timeout
+
+
+
+
+
+ event_notification_command
+
+
+
+
+
+ event_notifications
+
+
+
+
+
+ failover
+
+
+
+
+
+ follow_command
+
+
+
+
+
+ log_facility
+
+
+
+
+
+ log_file
+
+
+
+
+
+ log_level
+
+
+
+
+
+ log_status_interval
+
+
+
+
+
+ monitor_interval_secs
+
+
+
+
+
+ monitoring_history
+
+
+
+
+
+ primary_notification_timeout
+
+
+
+
+
+ promote_command
+
+
+
+
+
+ reconnect_attempts
+
+
+
+
+
+ reconnect_interval
+
+
+
+
+
+ repmgrd_standby_startup_timeout
+
+
+
+
+
+
+ The following set of configuration file parameters must be updated via
+ repmgr standby register --force,
+ as they require changes to the repmgr.nodes table so they are visible to
+ all nodes in the replication cluster:
+
+
+
+
+
+ node_id
+
+
+
+
+
+ node_name
+
+
+
+
+
+ data_directory
+
+
+
+
+
+ location
+
+
+
+
+
+
+ priority
+
+
+
+
+
+
+
+ After executing repmgr standby register --force,
+ repmgrd must be restarted for the changes to take effect.
+
+
+
+
+