sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-04 00:02:37 -04:00
Code Issues Projects Releases Wiki Activity

Clarify tar documentation about return error codes.

Browse Source 
Backpatch to 8.2.X.
This commit is contained in:
Bruce Momjian 2007-09-14 13:26:36 +00:00
parent 6f5d343405
commit 7e82fa8b7a
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.95.2.1 2007/09/14 04:16:44 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.95.2.2 2007/09/14 13:26:36 momjian Exp $ -->
<chapter id="backup">
<title>Backup and Restore</title>
@ -719,11 +719,11 @@ SELECT pg_stop_backup();
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 was truncated while
<application>tar</> is copying it. Fortunately, GNU
<application>tar</> versions 1.16 and later exits with <literal>1</>
if a file was changed during the backup, and <literal>2</> for other
errors.
<application>tar</> return an error code indistinguishable from a
fatal error if a file was truncated while <application>tar</> was
copying it. Fortunately, GNU <application>tar</> versions 1.16 and
later exits with <literal>1</> if a file was changed during the backup,
and <literal>2</> for other errors.
</para>
<para>