Update GNU tar error code documentation.

Backpatch to 8.2.X.

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index e945ab1464350cba0364ec1e8742273b5e0790f9..b8b3bb01d91213e4b695955f0f99513690c883ab 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Backup and Restore
@@ -729,16 +729,17 @@ SELECT pg_stop_backup();
    
     Some backup tools that you might wish to use emit warnings or errors
     if the files they are trying to copy change while the copy proceeds.
-    This situation is normal, and not an error, when taking a base backup of
-    an active database; so you need to ensure that you can distinguish
+    This situation is normal, and not an error, when taking a base backup
+    of an active database; so you need to ensure that you can distinguish
     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.  Fortunately, GNU
-    tar versions 1.16 and later exit with 1
-    if files changed during the backup, and 2 for other errors.
+    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 was truncated
+    while tar is copying it.  Fortunately, GNU
+    tar versions 1.16 and later exits with 1
+    if a file was changed during the backup, and 2 for other
+    errors.