Note that "conninfo" must not be a connection URI.

Per GitHub #321.
This commit is contained in:
Ian Barwick
2017-08-29 23:02:23 +09:00
parent 8fefb799ee
commit 657125a3fb
2 changed files with 7 additions and 3 deletions

View File

@@ -400,7 +400,8 @@ least the following parameters:
- `conninfo`: a valid connection string for the `repmgr` database on the - `conninfo`: a valid connection string for the `repmgr` database on the
*current* server. (On the standby, the database will not yet exist, but *current* server. (On the standby, the database will not yet exist, but
`repmgr` needs to know the connection details to complete the setup `repmgr` needs to know the connection details to complete the setup
process). process). *NOTE* this must be a keyword/value string, not a connection
URI; this limitation will be removed in a future `repmgr` version.
`repmgr.conf` should not be stored inside the PostgreSQL data directory, `repmgr.conf` should not be stored inside the PostgreSQL data directory,
as it could be overwritten when setting up or reinitialising the PostgreSQL as it could be overwritten when setting up or reinitialising the PostgreSQL

View File

@@ -26,11 +26,14 @@
# the server's hostname or another identifier unambiguously # the server's hostname or another identifier unambiguously
# associated with the server to avoid confusion # associated with the server to avoid confusion
# Database connection information as a conninfo string # Database connection information as a conninfo string (this must be a
# This must be accessible to all servers in the cluster; for details see: # keyword/value string, not a connection URI).
# #
# https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNSTRING # https://www.postgresql.org/docs/current/static/libpq-connect.html#LIBPQ-CONNSTRING
# #
# All servers in the cluster must be able to access the database
# using this connection string.
#
#conninfo='host=192.168.204.104 dbname=repmgr user=repmgr' #conninfo='host=192.168.204.104 dbname=repmgr user=repmgr'
# #
# If repmgrd is in use, consider explicitly setting `connect_timeout` in the # If repmgrd is in use, consider explicitly setting `connect_timeout` in the