From edc18429bdfffe9123760d481cd398454aa6a5ca Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 14 Sep 2007 04:15:50 +0000 Subject: [PATCH] Update GNU tar error code documentation. Backpatch to 8.2.X. --- doc/src/sgml/backup.sgml | 21 +++++++++++---------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index e945ab1464..b8b3bb01d9 100644 --- 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. -- 2.40.0