|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.144 2010/02/22 17:15:10 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.145 2010/03/31 23:35:19 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="backup"> |
4 | 4 | <title>Backup and Restore</title> |
@@ -604,11 +604,12 @@ cp -i pg_xlog/00000001000000A900000065 /mnt/server/archivedir/00000001000000A900 |
604 | 604 | directory). |
605 | 605 | It is advisable to test your proposed archive command to ensure that it |
606 | 606 | indeed does not overwrite an existing file, <emphasis>and that it returns |
607 | | - nonzero status in this case</>. We have found that <literal>cp -i</> does |
608 | | - this correctly on some platforms but not others. If the chosen command |
609 | | - does not itself handle this case correctly, you should add a command |
610 | | - to test for existence of the archive file. For example, something |
611 | | - like: |
| 607 | + nonzero status in this case</>. On many Unix platforms, <command>cp |
| 608 | + -i</> causes copy to prompt before overwriting a file, and |
| 609 | + <literal>< /dev/null</> causes the prompt (and overwriting) to |
| 610 | + fail. If your platform does not support this behavior, you should |
| 611 | + add a command to test for the existence of the archive file. For |
| 612 | + example, something like: |
612 | 613 | <programlisting> |
613 | 614 | archive_command = 'test ! -f .../%f && cp %p .../%f' |
614 | 615 | </programlisting> |
|