Re: Next Steps with Hash Indexes

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: Next Steps with Hash Indexes
Date: 2021-08-11 00:37:28
Message-ID: CAH2-WznD+m-=E4AyzD6R7iA3xd3KiDsbDk9CWu1Le2xgkA2R7w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 15, 2021 at 9:41 AM Simon Riggs
<simon(dot)riggs(at)enterprisedb(dot)com> wrote:
> It would be very desirable to allow Hash Indexes to become Primary Key
> Indexes, which requires both
> amroutine->amcanunique = true;
> amroutine->amcanmulticol = true;

Why do you say that? I don't think it's self-evident that it's desirable.

In general I don't think that hash indexes are all that compelling
compared to B-Trees. In practice the flexibility of B-Trees tends to
win out, even if B-Trees are slightly slower than hash indexes with
certain kinds of benchmarks that are heavy on point lookups and have
no locality.

I have no reason to object to any of this, and I don't object. I'm just asking.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2021-08-11 00:47:38 Re: [PATCH] test/ssl: rework the sslfiles Makefile target
Previous Message Michael Paquier 2021-08-11 00:35:21 Re: Quirk of pg_temp schemas ...