|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.72 2005/10/2221:56:07 tgl Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.73 2005/10/2222:09:49 tgl Exp $ |
3 | 3 | --> |
4 | 4 | <chapter id="backup"> |
5 | 5 | <title>Backup and Restore</title> |
@@ -676,6 +676,15 @@ SELECT pg_stop_backup(); |
676 | 676 | </orderedlist> |
677 | 677 | </para> |
678 | 678 |
|
| 679 | + <para> |
| 680 | + Some versions of GNU <application>tar</> consider it an error if a file |
| 681 | + is changed while <application>tar</> is copying it. This case is normal, |
| 682 | + and not an error, when taking a base backup of an active database. |
| 683 | + Since ignoring all errors from <application>tar</> would be unwise, |
| 684 | + you should either manually inspect <application>tar</>'s messages or |
| 685 | + else use a different backup tool that does not complain about this case. |
| 686 | + </para> |
| 687 | + |
679 | 688 | <para> |
680 | 689 | It is not necessary to be very concerned about the amount of time elapsed |
681 | 690 | between <function>pg_start_backup</> and the start of the actual backup, |
|