|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.76 2005/11/07 17:36:44 tgl Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.77 2006/02/24 14:03:01 momjian Exp $ |
3 | 3 | --> |
4 | 4 | <chapter id="backup"> |
5 | 5 | <title>Backup and Restore</title> |
@@ -744,12 +744,13 @@ SELECT pg_stop_backup(); |
744 | 744 | <function>pg_stop_backup</> and the archiving of all WAL segment |
745 | 745 | files needed to make the file system backup consistent. |
746 | 746 | </para> |
| 747 | + |
747 | 748 | <para> |
748 | 749 | The backup history file is just a small text file. It contains the |
749 | 750 | label string you gave to <function>pg_start_backup</>, as well as |
750 | | - the starting and ending timesof the backup. If you usedthelabel |
751 | | - to identify where the associated dump file is kept,then the |
752 | | - archived history file is enough to tell you which dump file to |
| 751 | + the starting and ending timesand WAL segments ofthebackup. |
| 752 | +If you used the labelto identify where the associated dump file is kept, |
| 753 | +then thearchived history file is enough to tell you which dump file to |
753 | 754 | restore, should you need to do so. |
754 | 755 | </para> |
755 | 756 |
|
|