From 5fb01d829a2cea3c4fdf0fc5ac3cb7c2057150ba Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Mon, 16 Jul 2007 22:20:51 +0000
Subject: [PATCH] Update docs that GNU tar versions >=1.16 exit with 1 on files
changed, 2 on other errors.
---
doc/src/sgml/backup.sgml | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 454c286715b..e945ab14643 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.98 2007/06/29 15:46:21 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.99 2007/07/16 22:20:51 momjian Exp $ -->
<chapter id="backup">
<title>Backup and Restore</title>
@@ -734,13 +734,11 @@ SELECT pg_stop_backup();
complaints of this sort from real errors. For example, some versions
of <application>rsync</> return a separate exit code for <quote>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 <application>tar</> consider it an error if a file
- is changed while <application>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 <application>tar</>'s messages.
- GNU <application>tar</> is therefore not the best tool for making base
- backups.
+ code as a non-error case. Also, some versions of GNU
+ <application>tar</> consider it an error if a file is changed while
+ <application>tar</> is copying it. Fortunately, GNU
+ <application>tar</> versions 1.16 and later exit with <literal>1</>
+ if files changed during the backup, and <literal>2</> for other errors.
</para>
<para>
--
GitLab