mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-22 22:56:29 +00:00
2341da7a06
Note that most entries still need a bit more tidying up, consistent structuring, provision of more examples etc.
42 lines
1.2 KiB
Plaintext
42 lines
1.2 KiB
Plaintext
<refentry id="repmgr-cluster-cleanup">
|
|
<indexterm>
|
|
<primary>repmgr cluster cleanup</primary>
|
|
</indexterm>
|
|
<refmeta>
|
|
<refentrytitle>repmgr cluster cleanup</refentrytitle>
|
|
</refmeta>
|
|
|
|
<refnamediv>
|
|
<refname>repmgr cluster cleanup</refname>
|
|
<refpurpose>purge monitoring history</refpurpose>
|
|
</refnamediv>
|
|
|
|
<refsect1>
|
|
<title>Description</title>
|
|
<para>
|
|
Purges monitoring history from the <literal>repmgr.monitoring_history</literal> table to
|
|
prevent excessive table growth. Use the <literal>-k/--keep-history</literal> to specify the
|
|
number of days of monitoring history to retain. This command can be used
|
|
manually or as a cronjob.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Usage</title>
|
|
<para>
|
|
This command requires a valid <filename>repmgr.conf</filename> file for the node on which it is
|
|
executed; no additional arguments are required.
|
|
</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>Notes</title>
|
|
|
|
<para>
|
|
Monitoring history will only be written if <application>repmgrd</application> is active, and
|
|
<varname>monitoring_history</varname> is set to <literal>true</literal> in
|
|
<filename>repmgr.conf</filename>.
|
|
</para>
|
|
</refsect1>
|
|
</refentry>
|