github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-28 09:26:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

repmgrd: restrict BDR monitoring to two node setup

Browse Source 
It's not safe to have more than two nodes with this kind of
"failover", so we don't need to select alternative nodes by
priority.
This commit is contained in:
Ian Barwick
2017-07-14 12:56:11 +09:00
parent 91c7013024
commit e3b3fb65f0
12 changed files with 96 additions and 212 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
repmgr.conf.sample
View File

@@ -13,7 +13,7 @@
# repmgr and repmgrd require the following items to be configured.
#node_id=1 # A unique integer greater than zero
#node_id= # A unique integer greater than zero
#node_name='' # An arbitrary (but unique) string; we recommend
# using the server's hostname or another identifier
# unambiguously associated with the server to avoid
@@ -28,6 +28,7 @@
#
# For details on conninfo strings, see:
# https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNSTRING
#
# 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
@@ -44,8 +45,9 @@
# Replication settings
#------------------------------------------------------------------------------
#replication_type=physical # Must be one of 'physical' or 'bdr'
#upstream_node_id=1 # When using cascading replication, a standby
#upstream_node_id= # When using cascading replication, a standby
# can connect to another upstream standby node
# which is specified by setting 'upstream_node_id'.
# In that case, the upstream node must exist