From 488afa9f7f62dcb4ad52d1e9c02ba79d745a9600 Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Fri, 22 Feb 2019 13:50:03 +0900
Subject: [PATCH] doc: clarify replication slot usage with Barman

Barman will usually use one replication slot, but that's generally
preferable to multiple slots.
---
 doc/cloning-standbys.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/cloning-standbys.sgml b/doc/cloning-standbys.sgml
index ab9dfe7b..7aa74bc7 100644
--- a/doc/cloning-standbys.sgml
+++ b/doc/cloning-standbys.sgml
@@ -243,8 +243,8 @@
     </simpara>
     <simpara>
      As an alternative we recommend using 2ndQuadrant's <ulink url="https://www.pgbarman.org/">Barman</ulink>,
-     which offloads WAL management to a separate server, negating the need to use replication
-     slots to reserve WAL. See section <xref linkend="cloning-from-barman">
+     which offloads WAL management to a separate server, removing the requirement to use a replication
+     slot for each individual standby to reserve WAL. See section <xref linkend="cloning-from-barman">
      for more details on using &repmgr; together with Barman.
     </simpara>
    </tip>