Update pitr docs to mention inclusive/exclusive xid specification

This commit is contained in:
Bruce Momjian 2004-08-07 18:07:46 +00:00
parent d48d86651c
commit ff2c8950fe

View File

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