Update pitr docs to mention inclusive/exclusive xid specification

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 49a6bb0ac123bf82016eac34bec17d2c558b83b0..4b2d9c995d280cbaf200760f6c1461170b3de19f 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,5 +1,5 @@
 
 
  Backup and Restore
@@ -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
     main transaction table), just specify the required stopping point in
     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.  Keep in mind that while transaction
-    IDs are asigned sequentially at transaction start, transactions can
-    complete in a different numeric order.
+    date/time or completion of a specific transaction ID.  The stop
+    specification can be inclusive or exclusive.  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.  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