From 5abec2bb97282d5cc346ec39f32970300aeb9c28 Mon Sep 17 00:00:00 2001 From: Ian Barwick 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 22b60e70..da6e28ee 100644 --- a/doc/cloning-standbys.sgml +++ b/doc/cloning-standbys.sgml @@ -243,8 +243,8 @@ As an alternative we recommend using 2ndQuadrant's Barman, - which offloads WAL management to a separate server, negating the need to use replication - slots to reserve WAL. See section + 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 for more details on using &repmgr; together with Barman.