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 eabd844fa381d24d443867512073170f111711ac..74684f7d0cc68d424235cc56ec1f6ab9e7fd644f 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 a28f1dba519473052e6102e0e356e41e05e91bb9..1b02f5f563543719dca13bc8c31657f2857f7491 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>