summaryrefslogtreecommitdiff
path: root/doc/development/hash_indexes.md
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axil@gitlab.com>2019-08-21 11:24:55 +0200
committerAchilleas Pipinellis <axil@gitlab.com>2019-08-21 11:24:55 +0200
commita39228db8027c966e8117d40766b0cef4fbd50f6 (patch)
tree143045af7214ae6746e7b7c9df647c71ec2bd675 /doc/development/hash_indexes.md
parent05f50c9b52fde54513fe55fef97499b35719eae2 (diff)
parentaed489bf901745ced6618e680913d0d213998923 (diff)
downloadgitlab-ce-docs-zm002-gitlab-case.tar.gz
Merge branch 'master' into docs-zm002-gitlab-casedocs-zm002-gitlab-case
Diffstat (limited to 'doc/development/hash_indexes.md')
-rw-r--r--doc/development/hash_indexes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/hash_indexes.md b/doc/development/hash_indexes.md
index e6c1b3590b1..417ea18e22f 100644
--- a/doc/development/hash_indexes.md
+++ b/doc/development/hash_indexes.md
@@ -1,6 +1,6 @@
# Hash Indexes
-Both PostgreSQL and MySQL support hash indexes besides the regular btree
+PostgreSQL supports hash indexes besides the regular btree
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