|
1 | 1 | <!--
|
2 |
| -$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.44 2004/08/0712:21:25 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.45 2004/08/0718:07:46 momjian Exp $ |
3 | 3 | -->
|
4 | 4 | <chapter id="backup">
|
5 | 5 | <title>Backup and Restore</title>
|
@@ -813,11 +813,12 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
|
813 | 813 | some previous point in time (say, right before the junior DBA dropped your
|
814 | 814 | main transaction table), just specify the required stopping point in
|
815 | 815 | <literal>recovery.conf</>. You can specify the stop point either by
|
816 |
| - date/time or by transaction ID. As of this writing only the date/time |
817 |
| - option is very usable, since there are no tools to help you identify |
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. |
| 816 | + date/time or completion of a specific transaction ID. The stop |
| 817 | + specification can be inclusive or exclusive. As of this writing |
| 818 | + only the date/time option is very usable, since there are no tools |
| 819 | + to help you identify which transaction ID to use. Keep in mind |
| 820 | + that while transaction IDs are asigned sequentially at transaction |
| 821 | + start, transactions can complete in a different numeric order. |
821 | 822 | </para>
|
822 | 823 | <para>
|
823 | 824 | Note that the stop point must be after the ending time of the backup
|
|