Remove documentation mention that hash indexes perform no better than

btree;  keep mention about missing WAL logging.

Kenneth Marshall

diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
index f02a9579d14d52bf9bacf99df377ff965dff8360..c09cd22689b81c5e6af5d6b7bcb93eaedea75a94 100644 (file)
--- a/doc/src/sgml/indices.sgml
+++ b/doc/src/sgml/indices.sgml
@@ -190,13 +190,10 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable>
 
   <note>
    <para>
-    Testing has shown <productname>PostgreSQL</productname>'s hash
-    indexes to perform no better than B-tree indexes, and the
-    index size and build time for hash indexes is much worse.
-    Furthermore, hash index operations are not presently WAL-logged,
+    Hash index operations are not presently WAL-logged,
     so hash indexes might need to be rebuilt with <command>REINDEX</>
     after a database crash.
-    For these reasons, hash index use is presently discouraged.
+    For this reason, hash index use is presently discouraged.
    </para>
   </note>