summaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorSimon Riggs <simon@2ndQuadrant.com>2016-09-03 17:48:01 +0100
committerSimon Riggs <simon@2ndQuadrant.com>2016-09-03 17:48:01 +0100
commit35250b6ad7a8ece5cfe54c0316c180df19f36c13 (patch)
tree1dd327fc181be356183701e34f45f95e2a9a60f4 /doc/src
parent0c40ab3a88edf654165e562deee0c303a6ebef5e (diff)
New recovery target recovery_target_lsn
Michael Paquier
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/recovery-config.sgml24
1 files changed, 21 insertions, 3 deletions
diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml
index 26af221745c..de3fb10f5be 100644
--- a/doc/src/sgml/recovery-config.sgml
+++ b/doc/src/sgml/recovery-config.sgml
@@ -157,9 +157,10 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
By default, recovery will recover to the end of the WAL log. The
following parameters can be used to specify an earlier stopping point.
At most one of <varname>recovery_target</>,
- <varname>recovery_target_name</>, <varname>recovery_target_time</>, or
- <varname>recovery_target_xid</> can be used; if more than one of these
- is specified in the configuration file, the last entry will be used.
+ <varname>recovery_target_lsn</>, <varname>recovery_target_name</>,
+ <varname>recovery_target_time</>, or <varname>recovery_target_xid</>
+ can be used; if more than one of these is specified in the configuration
+ file, the last entry will be used.
</para>
<variablelist>
@@ -232,6 +233,23 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
</para>
</listitem>
</varlistentry>
+
+ <varlistentry id="recovery-target-lsn" xreflabel="recovery_target_lsn">
+ <term><varname>recovery_target_lsn</varname> (<type>pg_lsn</type>)
+ <indexterm>
+ <primary><varname>recovery_target_lsn</> recovery parameter</primary>
+ </indexterm>
+ </term>
+ <listitem>
+ <para>
+ This parameter specifies the LSN of the transaction log location up
+ to which recovery will proceed. The precise stopping point is also
+ influenced by <xref linkend="recovery-target-inclusive">. This
+ parameter is parsed using the system data type
+ <link linkend="datatype-pg-lsn"><type>pg_lsn</></link>.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
<para>