Add some notes about unimplemented aspects of PITR backup/recovery.

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 3b45ec17def8c7bc3666537bddb2d75a9c743c2f..49b3afa4f739b0b305d2220242d180230eebc50f 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,5 +1,5 @@
 
 
  Backup and Restore
@@ -891,6 +891,35 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
     timelines that branched off earlier than the base backup.
    
   
+
+  
+   Caveats
+
+   
+    At this writing, there are several limitations of the on-line backup
+    technique.  These will probably be fixed in future releases.
+
+  
+   
+    
+     The effects of CREATE DATABASE, DROP DATABASE,
+     CREATE TABLESPACE, and DROP TABLESPACE are
+     not fully reflected in the WAL log.  It is recommended that you take
+     a new base backup after performing one of these operations.
+    
+   
+   
+    
+     Operations on non-btree indexes (hash, R-tree, and GiST indexes) are
+     not presently WAL-logged, so replay will not update these index types.
+     The recommended workaround, if you use any non-btree indexes, is to
+     manually REINDEX each such index after completing a
+     recovery operation.
+    
+   
+  
+   
+