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

@@ -1288,7 +1288,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</literal> or <literal>.history</literal>. Also be aware that
+    <literal>.history</literal>. Also be aware that
     the base name of the <literal>%p</literal> path will be different from
     <literal>%f</literal>; do not expect them to be interchangeable.
    </para>

doc/src/sgml/high-availability.sgml

@@ -1524,7 +1524,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</literal> or
+    it to appear. For files ending in 
     <literal>.history</literal> there is no need to wait, and a non-zero return
     code must be returned. A waiting <varname>restore_command</varname> can be
     written as a custom script that loops after polling for the existence of