From: Fujii Masao Date: Tue, 26 Jun 2018 15:45:21 +0000 (+0900) Subject: Fix documentation bug related to backup history file. X-Git-Tag: REL9_3_24~26 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=833397e73e2e8d8e37aa38b31e00320161bb6ff8;p=thirdparty%2Fpostgresql.git 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 --- diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 969318b4ae5..798580291be 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1083,7 +1083,7 @@ restore_command = 'cp /mnt/server/archivedir/%f %p' in the archive; it must return nonzero when so asked. This is not an error condition. 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 2d5d23526b8..af661eb96ed 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1261,7 +1261,7 @@ primary_conninfo = 'host=192.168.1.50 port=5432 user=foo password=foopass' 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