diff options
| author | Fujii Masao <fujii@postgresql.org> | 2018-06-27 00:45:21 +0900 |
|---|---|---|
| committer | Fujii Masao <fujii@postgresql.org> | 2018-06-27 00:51:32 +0900 |
| commit | ef2deca1b77ebcbd554eaa8dfcd5e653ea67593b (patch) | |
| tree | 401248e47f4bc5b7eb96610d5a8a9d10a6f521f7 | |
| parent | 3bc19d0d263c32c225a391e5275d6ba24dbc423c (diff) | |
| download | postgresql-ef2deca1b77ebcbd554eaa8dfcd5e653ea67593b.tar.gz | |
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.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index bfb86f4255..02c61546de 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1122,7 +1122,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 f1819b0bf7..35daf0103a 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1383,7 +1383,7 @@ primary_slot_name = 'node_a_slot' 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 |