|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/indices.sgml,v 1.75 2008/09/23 09:20:34 heikki Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/indices.sgml,v 1.76 2009/02/0720:05:44 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="indexes"> |
4 | 4 | <title id="indexes-title">Indexes</title> |
@@ -190,13 +190,10 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable> |
190 | 190 |
|
191 | 191 | <note> |
192 | 192 | <para> |
193 | | - Testing has shown <productname>PostgreSQL</productname>'s hash |
194 | | - indexes to perform no better than B-tree indexes, and the |
195 | | - index size and build time for hash indexes is much worse. |
196 | | - Furthermore, hash index operations are not presently WAL-logged, |
| 193 | + Hash index operations are not presently WAL-logged, |
197 | 194 | so hash indexes might need to be rebuilt with <command>REINDEX</> |
198 | 195 | after a database crash. |
199 | | - Forthese reasons, hash index use is presently discouraged. |
| 196 | + Forthis reason, hash index use is presently discouraged. |
200 | 197 | </para> |
201 | 198 | </note> |
202 | 199 |
|
|