From b84f217710966030c601e0488eca48ba818eb338 Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Wed, 31 Oct 2018 10:27:37 +0900 Subject: [PATCH] doc: note repmgr extension can be installed manually --- doc/repmgr-primary-register.sgml | 29 +++++++++++++++++++---------- 1 file changed, 19 insertions(+), 10 deletions(-) diff --git a/doc/repmgr-primary-register.sgml b/doc/repmgr-primary-register.sgml index 8f2b0a87..299e0422 100644 --- a/doc/repmgr-primary-register.sgml +++ b/doc/repmgr-primary-register.sgml @@ -21,6 +21,15 @@ installing the &repmgr; extension. This command needs to be executed before any standby nodes are registered. + + + + It's possibly to install the &repmgr; extension manually before executing + repmgr primary register; in this case &repmgr; will + detect the presence of the extension and skip that step. + + + @@ -35,16 +44,16 @@ - - If providing the configuration file location with , - avoid using a relative path, as &repmgr; stores the configuration file location - in the repmgr metadata for use when &repmgr; is executed remotely (e.g. during - ). &repmgr; will attempt to convert the - a relative path into an absolute one, but this may not be the same as the path you - would explicitly provide (e.g. ./repmgr.conf might be converted - to /path/to/./repmgr.conf, whereas you'd normally write - /path/to/repmgr.conf). - + + If providing the configuration file location with , + avoid using a relative path, as &repmgr; stores the configuration file location + in the repmgr metadata for use when &repmgr; is executed remotely (e.g. during + ). &repmgr; will attempt to convert the + a relative path into an absolute one, but this may not be the same as the path you + would explicitly provide (e.g. ./repmgr.conf might be converted + to /path/to/./repmgr.conf, whereas you'd normally write + /path/to/repmgr.conf). +