Note explicitly that hash indexes are also not replicated because they're not

WAL-logged. Make the notice about the lack of WAL-logging more visible by
making it a . Also remove the false statement from hot standby
caveats section that hash indexes are not used during hot standby.

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 1f5ec85ecaeaf1e81255600efd5d60710145ffd4..bbcc6b6822034ba0daeacb02a1f2bc381778785a 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1845,8 +1845,7 @@ LOG:  database system is ready to accept read only connections
    
     
      Operations on hash indexes are not presently WAL-logged, so
-     replay will not update these indexes.  Hash indexes will not be
-     used for query plans during recovery.
+     replay will not update these indexes.
     
    
    

diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
index 15c3320e2fdb2ba683b8b3c255d1014bf3350a42..98d5b38ed6c73e687f75ce61ff717f9baf030960 100644 (file)
--- a/doc/src/sgml/indices.sgml
+++ b/doc/src/sgml/indices.sgml
@@ -187,14 +187,15 @@ CREATE INDEX name ON table
 
   
 
-  <note>
+  <caution>
    
     Hash index operations are not presently WAL-logged,
     so hash indexes might need to be rebuilt with REINDEX
-    after a database crash.
-    For this reason, hash index use is presently discouraged.
+    after a database crash. They are also not replicated over streaming or
+    file-based replication.
+    For these reasons, hash index use is presently discouraged.
    
-  note>
+  caution>