Why is Hash index not transaction safe.

From: Wei Shan <weishan(dot)ang(at)gmail(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: Why is Hash index not transaction safe.
Date: 2015-05-04 03:26:30
Message-ID: CAFe9ZTpb+4G0sfBXApFpKs2ypuyQHPF-r899E+5jvfsx6uzvCw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Hi all,

I read the following about Hash indexes in Heroku's blog (
https://devcenter.heroku.com/articles/postgresql-indexes)

*Hash Indexes are only useful for equality comparisons, but you pretty much
never want to use them since they are not transaction safe, need to be
manually rebuilt after crashes, and are not replicated to followers, so the
advantage over using a B-Tree is rather small.*

Could anyone explain about why is it not transaction safe as compared to
B-Tree index.

Thanks!
--
Regards,
Ang Wei Shan

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2015-05-04 04:11:33 Re: Why is Hash index not transaction safe.
Previous Message Felipe Santos 2015-04-30 12:16:13 Re: Using postgreSQL in our clinic