mirrors
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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

on other errors.
This commit is contained in:
Bruce Momjian 2007-07-16 22:20:51 +00:00
parent 2a275e6d3c
commit 5fb01d829a
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/src/sgml/backup.sgml
View File

@ -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>