mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-26 00:26:30 +00:00
doc: clarify replication slot FAQ entry
This commit is contained in:
@@ -35,15 +35,25 @@
|
|||||||
<para>
|
<para>
|
||||||
Replication slots, introduced in PostgreSQL 9.4, ensure that the
|
Replication slots, introduced in PostgreSQL 9.4, ensure that the
|
||||||
primary server will retain WAL files until they have been consumed
|
primary server will retain WAL files until they have been consumed
|
||||||
by all standby servers. This makes WAL file management much easier,
|
by all standby servers. This means standby servers should never
|
||||||
and if used &repmgr; will no longer insist on a fixed minimum number
|
fail due to not being able to retrieve required WAL files from the
|
||||||
(default: 5000) of WAL files being retained.
|
primary.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
However this does mean that if a standby is no longer connected to the
|
However this does mean that if a standby is no longer connected to the
|
||||||
primary, the presence of the replication slot will cause WAL files
|
primary, the presence of the replication slot will cause WAL files
|
||||||
to be retained indefinitely.
|
to be retained indefinitely, and eventually lead to disk space
|
||||||
|
exhaustion.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<tip>
|
||||||
|
<para>
|
||||||
|
2ndQuadrant's recommended configuration is to configure
|
||||||
|
<ulink url="https://www.pgbarman.org/">Barman</ulink> as a fallback
|
||||||
|
source of WAL files, rather than maintain replication slots for
|
||||||
|
each standby. See also: <link linkend="cloning-from-barman-restore-command">Using Barman as a WAL file source</link>.
|
||||||
|
</para>
|
||||||
|
</tip>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2 id="faq-replication-slots-number" xreflabel="Number of replication slots">
|
<sect2 id="faq-replication-slots-number" xreflabel="Number of replication slots">
|
||||||
|
|||||||
Reference in New Issue
Block a user