Update docs that GNU tar versions >=1.16 exit with 1 on files changed, 2

on other errors.

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 454c286715bbb37c4230b978c7f095451b748b69..e945ab1464350cba0364ec1e8742273b5e0790f9 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Backup and Restore
@@ -734,13 +734,11 @@ SELECT pg_stop_backup();
     complaints of this sort from real errors.  For example, some versions
     of rsync return a separate exit code for vanished
     source files, and you can write a driver script to accept this exit
-    code as a non-error case.  Also,
-    some versions of GNU tar consider it an error if a file
-    is changed while tar is copying it.  There does not seem
-    to be any very convenient way to distinguish this error from other types
-    of errors, other than manual inspection of tar's messages.
-    GNU tar is therefore not the best tool for making base
-    backups.
+    code as a non-error case.  Also, some versions of GNU
+    tar consider it an error if a file is changed while
+    tar is copying it.  Fortunately, GNU
+    tar versions 1.16 and later exit with 1
+    if files changed during the backup, and 2 for other errors.