From a1c2ed7b0287fa58975eca20faae5c72877de30f Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sat, 7 Aug 2004 03:21:11 +0000 Subject: [PATCH] Mention that transactions can complete in a different numeric order, for PITR recovery. --- doc/src/sgml/backup.sgml | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 49b3afa4f7..70c49ee6e9 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1,5 +1,5 @@ Backup and Restore @@ -815,12 +815,16 @@ restore_command = 'cp /mnt/server/archivedir/%f %p' recovery.conf. You can specify the stop point either by date/time or by transaction ID. As of this writing only the date/time option is very usable, since there are no tools to help you identify - which transaction ID to use. Note that the stop point must be after - the ending time of the backup (ie, the time of - pg_stop_backup). You cannot use a base backup to recover - to a time when that backup was still going on. (To recover to such - a time, you must go back to your previous base backup and roll forward - from there.) + which transaction ID to use. Keep in mind that while transaction + IDs are asigned sequentially at transaction start, transactions can + complete in a different numeric order. + + Note that the stop point must be after the ending time of the backup + (ie, the time of pg_stop_backup). You cannot use a base + backup to recover to a time when that backup was still going on. (To + recover to such a time, you must go back to your previous base backup + and roll forward from there.)