|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.100 2007/09/1404:15:50 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.101 2007/09/1413:26:22 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="backup">
|
4 | 4 | <title>Backup and Restore</title>
|
@@ -735,11 +735,11 @@ SELECT pg_stop_backup();
|
735 | 735 | of <application>rsync</> return a separate exit code for
|
736 | 736 | <quote>vanished source files</>, and you can write a driver script to
|
737 | 737 | accept this exit code as a non-error case. Also, some versions of
|
738 |
| - GNU <application>tar</>consider itan errorif a file was truncated |
739 |
| - while <application>tar</>is copying it. Fortunately, GNU |
740 |
| - <application>tar</> versions 1.16 and later exits with <literal>1</> |
741 |
| - if a file was changed during the backup, and <literal>2</> for other |
742 |
| - errors. |
| 738 | + GNU <application>tar</>returnan errorcode indistinguishable from |
| 739 | +a fatal error if a file was truncatedwhile <application>tar</>was |
| 740 | +copying it. Fortunately, GNU<application>tar</> versions 1.16 and |
| 741 | +later exits with <literal>1</>if a file was changed during the backup, |
| 742 | +and <literal>2</> for othererrors. |
743 | 743 | </para>
|
744 | 744 |
|
745 | 745 | <para>
|
|