I guess the creating hash index is O(n), while use it to access data also get O(n), so,it's better than b-tree index ?
From the manual:
Note: Testing has shown PostgreSQL's hash indexes to perform no better than B-tree indexes, and the index size and build time for hash indexes is much worse. Furthermore, hash index operations are not presently WAL-logged, so hash indexes might need to be rebuilt with REINDEX after a database crash. For these reasons, hash index use is presently discouraged.
Later versions of the manual don't mention the performance issues, only focus on problems with replication.
It looks like it doesn't make sense to use a hash index.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With