From e8b5b92893db5db5daca2f160cfd8b05f183d20e Mon Sep 17 00:00:00 2001 From: Ian Barwick Date: Thu, 3 Oct 2019 15:52:32 +0900 Subject: [PATCH] doc: improve Barman standby clone example --- doc/cloning-standbys.xml | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/doc/cloning-standbys.xml b/doc/cloning-standbys.xml index d6ed6be5..efa6aec3 100644 --- a/doc/cloning-standbys.xml +++ b/doc/cloning-standbys.xml @@ -125,23 +125,19 @@ It's now possible to clone a standby from Barman, e.g.: - NOTICE: using configuration file "/etc/repmgr.conf" + $ repmgr -f /etc/repmgr.conf -h node1 -U repmgr -d repmgr standby clone NOTICE: destination directory "/var/lib/postgresql/data" provided - INFO: connecting to Barman server to verify backup for test_cluster + INFO: connecting to Barman server to verify backup for "test_cluster" INFO: checking and correcting permissions on existing directory "/var/lib/postgresql/data" INFO: creating directory "/var/lib/postgresql/data/repmgr"... INFO: connecting to Barman server to fetch server parameters - INFO: connecting to upstream node - INFO: connected to source node, checking its state - INFO: successfully connected to source node - DETAIL: current installation size is 29 MB + INFO: connecting to source node + DETAIL: current installation size is 30 MB NOTICE: retrieving backup from Barman... - receiving file list ... (...) NOTICE: standby clone (from Barman) complete NOTICE: you can now start your PostgreSQL server HINT: for example: pg_ctl -D /var/lib/postgresql/data start -