|
|
|
@ -428,6 +428,18 @@ Indexes: |
|
|
|
they can be useful. |
|
|
|
they can be useful. |
|
|
|
</para> |
|
|
|
</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 warm standby |
|
|
|
|
|
|
|
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> |
|
|
|
<para> |
|
|
|
Currently, only the B-tree, GiST and GIN index methods support |
|
|
|
Currently, only the B-tree, GiST and GIN index methods support |
|
|
|
multicolumn indexes. Up to 32 fields can be specified by default. |
|
|
|
multicolumn indexes. Up to 32 fields can be specified by default. |
|
|
|
|