mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-25 16:16:29 +00:00
doc: update witness server notes
- clarify that a separate PostgreSQL instance is needed for each witness server - remove historical 3.x reference
This commit is contained in:
@@ -79,13 +79,17 @@
|
|||||||
as otherwise if the primary server fails due to hardware issues, the witness
|
as otherwise if the primary server fails due to hardware issues, the witness
|
||||||
server will be lost too.
|
server will be lost too.
|
||||||
</para>
|
</para>
|
||||||
<note>
|
<important>
|
||||||
<simpara>
|
<simpara>
|
||||||
&repmgr; 3.3 and earlier provided a <command>repmgr create witness</command>
|
A PostgreSQL instance can only accommodate a single witness server.
|
||||||
command, which would automatically create a PostgreSQL instance. However
|
|
||||||
this often resulted in an unsatisfactory, hard-to-customise instance.
|
|
||||||
</simpara>
|
</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>
|
<para>
|
||||||
The witness server should be configured in the same way as a normal
|
The witness server should be configured in the same way as a normal
|
||||||
&repmgr; node; see section <xref linkend="configuration"/>.
|
&repmgr; node; see section <xref linkend="configuration"/>.
|
||||||
|
|||||||
Reference in New Issue
Block a user