docs: Note the recovery_min_apply_delay bloats pg_wal.

Those WAL files that we're waiting to apply have to be stored
somewhere.

Thom Brown

Discussion: http://postgr.es/m/CAA-aLv4SkJRK6GGcd0Axt8kt6_eWMEbtG7f8NJpFh+rNshtdNA@mail.gmail.com
This commit is contained in:
Robert Haas 2022-04-08 11:02:59 -04:00
parent e0064f0ff6
commit ad385a494f
1 changed files with 6 additions and 0 deletions

View File

@ -4872,6 +4872,12 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
state, until the standby is promoted or triggered. After that the standby state, until the standby is promoted or triggered. After that the standby
will end recovery without further waiting. will end recovery without further waiting.
</para> </para>
<para>
WAL records must be kept on the standby until they are ready to be
applied. Therefore, longer delays will result in a greater accumulation
of WAL files, increasing disk space requirements for the standby's
<filename>pg_wal</filename> directory.
</para>
<para> <para>
This parameter is intended for use with streaming replication deployments; This parameter is intended for use with streaming replication deployments;
however, if the parameter is specified it will be honored in all cases however, if the parameter is specified it will be honored in all cases