From e043d5c9a99d0ba565f365569c4cdf43e54878e1 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Wed, 21 Sep 2016 08:43:45 +0900 Subject: [PATCH] Clarify requirements for passwordless SSH access This is already effectively optional; in 3.2 we will ensure it becomes fully optional (mainly by deprecating --ignore-external-config-files and replacing it with --copy-external-config-files). --- README.md | 13 ++++++++++--- repmgr.c | 2 +- 2 files changed, 11 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 0d638e39..8cd407bb 100644 --- a/README.md +++ b/README.md @@ -145,10 +145,17 @@ The `repmgr` tools must be installed on each server in the replication cluster. A dedicated system user for `repmgr` is *not* required; as many `repmgr` and `repmgrd` actions require direct access to the PostgreSQL data directory, -it should be executed by the `postgres` user. +these commands should be executed by the `postgres` user. -Additionally, we recommend installing `rsync` and enabling passwordless -`ssh` connectivity between all servers in the replication cluster. +Passwordless `ssh` connectivity between all servers in the replication cluster +is not required, but is necessary in the following cases: + +* if you need `repmgr` to copy configuration files from outside the PostgreSQL + data directory +* to perform switchover operations +* when using `rsync` to clone a standby + +In these cases `rsync` is required on all servers too. * * * diff --git a/repmgr.c b/repmgr.c index 45e8b94f..7ddc6465 100644 --- a/repmgr.c +++ b/repmgr.c @@ -4329,7 +4329,7 @@ do_standby_switchover(void) { /* * For 9.3/9.4, if pg_rewind is not available on the remote server, - * we'll need to force a reclone of the standby sing rsync - this may + * we'll need to force a reclone of the standby using rsync - this may * take some time on larger databases, so use with care! * * Note that following this clone we'll be using `repmgr standby follow`