|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.98 2007/06/29 15:46:21 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.99 2007/07/16 22:20:51 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="backup">
|
4 | 4 | <title>Backup and Restore</title>
|
@@ -734,13 +734,11 @@ SELECT pg_stop_backup();
|
734 | 734 | complaints of this sort from real errors. For example, some versions
|
735 | 735 | of <application>rsync</> return a separate exit code for <quote>vanished
|
736 | 736 | source files</>, and you can write a driver script to accept this exit
|
737 |
| - code as a non-error case. Also, |
738 |
| - some versions of GNU <application>tar</> consider it an error if a file |
739 |
| - is changed while <application>tar</> is copying it. There does not seem |
740 |
| - to be any very convenient way to distinguish this error from other types |
741 |
| - of errors, other than manual inspection of <application>tar</>'s messages. |
742 |
| - GNU <application>tar</> is therefore not the best tool for making base |
743 |
| - backups. |
| 737 | + code as a non-error case. Also, some versions of GNU |
| 738 | + <application>tar</> consider it an error if a file is changed while |
| 739 | + <application>tar</> is copying it. Fortunately, GNU |
| 740 | + <application>tar</> versions 1.16 and later exit with <literal>1</> |
| 741 | + if files changed during the backup, and <literal>2</> for other errors. |
744 | 742 | </para>
|
745 | 743 |
|
746 | 744 | <para>
|
|