summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2018-06-27 00:45:21 +0900
committerFujii Masao <fujii@postgresql.org>2018-06-27 00:49:47 +0900
commit09879f7536350e53ca21319b80430fb244bddfe7 (patch)
tree1dd0755cbb5a3b7a4e68905738f84db982167fb8
parent3566873f21909397561418fab22c98332fa8b72a (diff)
Fix documentation bug related to backup history file.
The backup history file has been no longer necessary for recovery since the version 9.0. It's now basically just for informational purpose. But previously the documentations still described that a recovery requests the backup history file to proceed. The commit fixes this documentation bug. Back-patch to all supported versions. Author: Yugo Nagata Reviewed-by: Kyotaro Horiguchi Discussion: https://postgr.es/m/20180626174752.0ce505e3.nagata@sraoss.co.jp
-rw-r--r--doc/src/sgml/backup.sgml2
-rw-r--r--doc/src/sgml/high-availability.sgml2
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index c31f87073a0..f2bbff7bdb8 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1282,7 +1282,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
<para>
Not all of the requested files will be WAL segment
files; you should also expect requests for files with a suffix of
- <literal>.backup</> or <literal>.history</>. Also be aware that
+ <literal>.history</literal>. Also be aware that
the base name of the <literal>%p</> path will be different from
<literal>%f</>; do not expect them to be interchangeable.
</para>
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 2737b310b24..2773cec9b8d 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1518,7 +1518,7 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
processing would request a file from the WAL archive, reporting failure
if the file was unavailable. For standby processing it is normal for
the next WAL file to be unavailable, so the standby must wait for
- it to appear. For files ending in <literal>.backup</> or
+ it to appear. For files ending in
<literal>.history</> there is no need to wait, and a non-zero return
code must be returned. A waiting <varname>restore_command</> can be
written as a custom script that loops after polling for the existence of