postgres.git / summary / log / commit / refs

commit    d06d92cd2d5e3c3dd893ee0d82d14d1f8adbc82b
Author:   Fujii Masao <fujii@postgresql.org>
Date:     Tue Jun 26 15:45:21 2018 +0000

    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


 doc/src/sgml/backup.sgml            | 2 +-
 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 68132bbdacb..76b55433426 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1258,7 +1258,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 3dc437df246..a52580e3dd5 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1436,7 +1436,7 @@ synchronous_standby_names = '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


[parent: b5b973ef0ba7]