Commit e04a53a6 authored by Peter Eisentraut's avatar Peter Eisentraut

doc: Further clarify how recovery target parameters are applied

Recovery target parameters are all applied even in standby mode.  The
previous documentation mostly wished they were not but this was never
the case.

Discussion: https://www.postgresql.org/message-id/flat/e445616d-023e-a268-8aa1-67b8b335340c%40pgmasters.net
parent 2c97f734
...@@ -3152,13 +3152,11 @@ include_dir 'conf.d' ...@@ -3152,13 +3152,11 @@ include_dir 'conf.d'
recovery when the end of archived WAL is reached, but will keep trying to recovery when the end of archived WAL is reached, but will keep trying to
continue recovery by connecting to the sending server as specified by the continue recovery by connecting to the sending server as specified by the
<varname>primary_conninfo</varname> setting and/or by fetching new WAL <varname>primary_conninfo</varname> setting and/or by fetching new WAL
segments using <varname>restore_command</varname>. In this mode, you can segments using <varname>restore_command</varname>. For this mode, the
use parameters in both <xref parameters from this section and <xref
linkend="runtime-config-wal-archive-recovery"/> and <xref linkend="runtime-config-replication-standby"/> are of interest.
linkend="runtime-config-replication-standby"/>. Parameters from Parameters from <xref linkend="runtime-config-wal-recovery-target"/> will
<xref linkend="runtime-config-wal-recovery-target"/> will not be used, also be applied but are typically not useful in this mode.
with the exception of <xref linkend="guc-recovery-target-timeline"/>
which allows a timeline to be selected for recovery.
</para> </para>
<para> <para>
...@@ -3168,10 +3166,10 @@ include_dir 'conf.d' ...@@ -3168,10 +3166,10 @@ include_dir 'conf.d'
<filename>recovery.signal</filename> files are created, standby mode <filename>recovery.signal</filename> files are created, standby mode
takes precedence. Targeted recovery mode ends when the archived WAL is takes precedence. Targeted recovery mode ends when the archived WAL is
fully replayed, or when <varname>recovery_target</varname> is reached. fully replayed, or when <varname>recovery_target</varname> is reached.
In this mode, you can use parameters from both <xref In this mode, the parameters from both this section and <xref
linkend="runtime-config-wal-archive-recovery"/> and <xref linkend="runtime-config-wal-recovery-target"/> will be used. Parameters
linkend="runtime-config-wal-recovery-target"/>. Parameters from <xref from <xref linkend="runtime-config-replication-standby"/> will not be
linkend="runtime-config-replication-standby"/> will not be used. used.
</para> </para>
<variablelist> <variablelist>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment