From f7b9e11d6fbbc6db8a9d677bda7df8f24998fa23 Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian.barwick@enterprisedb.com>
Date: Wed, 16 Mar 2022 10:26:47 +0900
Subject: [PATCH] doc: update witness server notes

- clarify that a separate PostgreSQL instance is needed for each
  witness server
- remove historical 3.x reference
---
 doc/repmgrd-automatic-failover.xml | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/doc/repmgrd-automatic-failover.xml b/doc/repmgrd-automatic-failover.xml
index 795afc61..5d71f0e8 100644
--- a/doc/repmgrd-automatic-failover.xml
+++ b/doc/repmgrd-automatic-failover.xml
@@ -79,13 +79,17 @@
    as otherwise if the primary server fails due to hardware issues, the witness
    server will be lost too.
  </para>
- <note>
+ <important>
    <simpara>
-     &repmgr; 3.3 and earlier provided a <command>repmgr create witness</command>
-     command, which would automatically create a PostgreSQL instance. However
-     this often resulted in an unsatisfactory, hard-to-customise instance.
+     A PostgreSQL instance can only accommodate a single witness server.
    </simpara>
- </note>
+   <simpara>
+     If you are planning to use a single server to support more than one
+     witness server, a separate PostgreSQL instance is required for each
+     witness server in use.
+   </simpara>
+ </important>
+
  <para>
    The witness server should be configured in the same way as a normal
    &repmgr; node; see section <xref linkend="configuration"/>.