|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.42 2004/08/04 17:37:09 tgl Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.43 2004/08/07 03:21:11 momjian Exp $ |
3 | 3 | --> |
4 | 4 | <chapter id="backup"> |
5 | 5 | <title>Backup and Restore</title> |
@@ -815,12 +815,16 @@ restore_command = 'cp /mnt/server/archivedir/%f %p' |
815 | 815 | <literal>recovery.conf</>. You can specify the stop point either by |
816 | 816 | date/time or by transaction ID. As of this writing only the date/time |
817 | 817 | option is very usable, since there are no tools to help you identify |
818 | | - which transaction ID to use. Note that the stop point must be after |
819 | | - the ending time of the backup (ie, the time of |
820 | | - <function>pg_stop_backup</>). You cannot use a base backup to recover |
821 | | - to a time when that backup was still going on. (To recover to such |
822 | | - a time, you must go back to your previous base backup and roll forward |
823 | | - from there.) |
| 818 | + which transaction ID to use. Keep in mind that while transaction |
| 819 | + IDs are asigned sequentially at transaction start, transactions can |
| 820 | + complete in a different numeric order. |
| 821 | + </para |
| 822 | + <para> |
| 823 | + Note that the stop point must be after the ending time of the backup |
| 824 | + (ie, the time of <function>pg_stop_backup</>). You cannot use a base |
| 825 | + backup to recover to a time when that backup was still going on. (To |
| 826 | + recover to such a time, you must go back to your previous base backup |
| 827 | + and roll forward from there.) |
824 | 828 | </para> |
825 | 829 | </sect2> |
826 | 830 |
|
|