2020-10-30 14:08:56 -04:00
---
2020-11-17 10:09:28 -05:00
stage: Enablement
group: Database
2020-11-26 01:09:20 -05:00
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2020-10-30 14:08:56 -04:00
---
2017-08-11 08:16:08 -04:00
# Hash Indexes
2020-06-03 02:08:34 -04:00
PostgreSQL supports hash indexes besides the regular B-tree
2017-08-11 08:16:08 -04:00
indexes. Hash indexes however are to be avoided at all costs. While they may
_sometimes_ provide better performance the cost of rehashing can be very high.
More importantly: at least until PostgreSQL 10.0 hash indexes are not
WAL-logged, meaning they are not replicated to any replicas. From the PostgreSQL
documentation:
> 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
> answers to queries that subsequently use them. For these reasons, hash index
> use is presently discouraged.
2020-04-22 14:09:52 -04:00
RuboCop is configured to register an offense when it detects the use of a hash
2017-08-11 08:16:08 -04:00
index.
2020-06-03 02:08:34 -04:00
Instead of using hash indexes you should use regular B-tree indexes.
