mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-27 08:39:28 +08:00
Clarify hash index caution and copy to CREATE INDEX docs
This commit is contained in:
parent
22cc3b35f4
commit
9f9695a0cd
@ -196,8 +196,10 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable>
|
||||
<para>
|
||||
Hash index operations are not presently WAL-logged,
|
||||
so hash indexes might need to be rebuilt with <command>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.
|
||||
</para>
|
||||
</caution>
|
||||
|
@ -466,6 +466,18 @@ Indexes:
|
||||
they can be useful.
|
||||
</para>
|
||||
|
||||
<caution>
|
||||
<para>
|
||||
Hash index operations are not presently WAL-logged,
|
||||
so hash indexes might need to be rebuilt with <command>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.
|
||||
</para>
|
||||
</caution>
|
||||
|
||||
<para>
|
||||
Currently, only the B-tree, GiST and GIN index methods support
|
||||
multicolumn indexes. Up to 32 fields can be specified by default.
|
||||
|
Loading…
Reference in New Issue
Block a user