From: Simon Riggs Date: Wed, 17 Oct 2012 07:27:27 +0000 (+0100) Subject: Clarify hash index caution and copy to CREATE INDEX docs X-Git-Tag: REL9_1_7~48 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3877b1fa17fc9003691d890cec5557c64db05462;p=postgresql Clarify hash index caution and copy to CREATE INDEX docs --- diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml index 2dedb153c0..c7c3211f1f 100644 --- a/doc/src/sgml/indices.sgml +++ b/doc/src/sgml/indices.sgml @@ -196,8 +196,10 @@ CREATE INDEX name ON table Hash index operations are not presently WAL-logged, so hash indexes might need to be rebuilt with REINDEX - after a database crash. They are also not replicated over streaming or - file-based replication. + after a database crash if there were unwritten changes. + Also, changes to hash indexes are not replicated over streaming or + file-based replication after the initial base backup, so they + give wrong anwers to queries that subsequently use them. For these reasons, hash index use is presently discouraged. diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml index 5d0ea4372f..8f266ed6d0 100644 --- a/doc/src/sgml/ref/create_index.sgml +++ b/doc/src/sgml/ref/create_index.sgml @@ -451,6 +451,18 @@ Indexes: they can be useful. + + + Hash index operations are not presently WAL-logged, + so hash indexes might need to be rebuilt with REINDEX + after a database crash if there were unwritten changes. + Also, changes to hash indexes are not replicated over streaming or + file-based replication after the initial base backup, so they + give wrong anwers to queries that subsequently use them. + For these reasons, hash index use is presently discouraged. + + + Currently, only the B-tree, GiST and GIN index methods support multicolumn indexes. Up to 32 fields can be specified by default.