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[email protected]

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index ef4074d97515f54fb397e581b8748184f994392a..f1441301908b7c5846594a2e1a05d6cf9fd53604 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1114,7 +1114,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
    
     Not all of the requested files will be WAL segment
     files; you should also expect requests for files with a suffix of
-    .backup or .history>. Also be aware that
+    .history>. Also be aware that
     the base name of the %p path will be different from
     %f; do not expect them to be interchangeable.
    

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index e4bbc5d1cf79f3edfe51dd8f9237ecd4100676ae..cd5305620d45c4c28428913e652f9b6eeb117dff 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1341,7 +1341,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 .backup or
+    it to appear. For files ending in 
     .history there is no need to wait, and a non-zero return
     code must be returned. A waiting restore_command can be
     written as a custom script that loops after polling for the existence of