From b1eef0a2129496b6883968c0d2a812a4f5c8770d Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Tue, 10 Oct 2017 10:49:35 +0900
Subject: [PATCH] Update upgrade document

---
 doc/upgrading-from-repmgr3.md | 19 +++++++++++--------
 1 file changed, 11 insertions(+), 8 deletions(-)

diff --git a/doc/upgrading-from-repmgr3.md b/doc/upgrading-from-repmgr3.md
index 04ec2c1f..89c4d8fe 100644
--- a/doc/upgrading-from-repmgr3.md
+++ b/doc/upgrading-from-repmgr3.md
@@ -4,10 +4,14 @@ Upgrading from repmgr 3
 The upgrade process consists of two steps:
 
     1) converting the repmgr.conf configuration files
-    2) upgrading the repmgr schema.
+    2) upgrading the repmgr schema
+
+A script is provided to assist with converting `repmgr.conf`.
+
+The schema upgrade (which converts the `repmgr` metadata into
+a packaged PostgreSQL extension) is normally carried out
+automatically when the `repmgr` extension is created.
 
-Scripts are provided to assist both with converting repmgr.conf
-and upgrading the schema.
 
 Converting repmgr.conf configuration files
 ------------------------------------------
@@ -57,11 +61,10 @@ is provided in `contrib/convert-config.pl`. Use like this:
     $ ./convert-config.pl /etc/repmgr.conf
     node_id=2
     node_name=node2
-    conninfo=host=localhost dbname=repmgr user=repmgr port=5602
-    pg_ctl_options='-l /tmp/postgres.5602.log'
-    pg_bindir=/home/barwick/devel/builds/HEAD/bin
+    conninfo=host=node2 dbname=repmgr user=repmgr connect_timeout=2
+    pg_ctl_options='-l /var/log/postgres/startup.log'
     rsync_options=--exclude=postgresql.local.conf --archive
-    log_level=DEBUG
+    log_level=INFO
     pg_basebackup_options=--no-slot
     data_directory=
 
@@ -80,7 +83,7 @@ Ensure `repmgrd` is not running, or any cron jobs which execute the
 `repmgr` binary.
 
 Install `repmgr4`; any `repmgr3` packages should be uninstalled
-(if not automatically installed already).
+(if not automatically uninstalled already).
 
 ### Manually create the repmgr extension