|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.63 2005/04/1813:11:04 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.64 2005/04/1817:40:40 momjian Exp $ |
3 | 3 | --> |
4 | 4 | <chapter id="backup"> |
5 | 5 | <title>Backup and Restore</title> |
@@ -741,10 +741,10 @@ SELECT pg_stop_backup(); |
741 | 741 | <literal>0000000100001234000055CD.007C9330.backup</>. (The second |
742 | 742 | number in the file name stands for an exact position within the WAL |
743 | 743 | file, and can ordinarily be ignored.) Once you have safely archived |
744 | | - the WAL segment files used during thefile system backup (as |
745 | | - specified in the backup history file), you can delete allarchived |
746 | | - WAL segments with names numerically less. Keep in mind thatonly |
747 | | - completed WAL segment files are archived, so there will be delay |
| 744 | + thefile system backup and theWAL segment files used during the |
| 745 | +backup (asspecified in the backup history file), you can delete all |
| 746 | +archivedWAL segments with names numerically less. Keep in mind that |
| 747 | +onlycompleted WAL segment files are archived, so there will be delay |
748 | 748 | between running <function>pg_stop_backup</> and the archiving of |
749 | 749 | all WAL segment files needed to make the file system backup |
750 | 750 | consistent. |
|