On Mon, Mar 3, 2014 at 8:12 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> As a GSoC student, I will implement WAL recovery of hash indexes using the
>> other index types' WAL code as a guide.
Frankly, I'm skeptical of the idea that hash indexes will ever really
be useful. I realize that that's a counter-intuitive conclusion, but
there are many things we could do to improve B-Tree CPU costs to make
them closer to those of hash indexes, without making them any less
flexible. I myself would much rather work on that, and intend to.
The O(1) cost seems attractive when you consider that that only
requires that we read one index page from disk to service any given
index scan, but in fact B-Trees almost always only require the same.
They are of course also much more flexible. The concurrency
characteristics B-Trees are a lot better understood. I sincerely
suggest that we forget about conventional hash table type indexes. I
fear they're a lost cause.
In response to
pgsql-students by date
|Next:||From: email@example.com||Date: 2014-04-30 12:55:44|
|Subject: Re: [HACKERS] GSoC on WAL-logging hash indexes|
|Previous:||From: Fabrízio de Royes Mello||Date: 2014-04-07 18:43:10|
|Subject: Re: unable to insert column using postgresql and C|
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2014-04-30 08:08:09|
|Subject: Re: Fix initdb for path with whitespace and at char|
|Previous:||From: Heikki Linnakangas||Date: 2014-04-30 06:35:23|
|Subject: Re: Considerer Harmful Considered Harmful|
pgsql-advocacy by date
|Next:||From: vincent elschot||Date: 2014-04-30 07:29:18|
|Subject: Re: Let's start talking features and "theme" for
|Previous:||From: Michael Alan Brewer||Date: 2014-04-28 20:01:56|
|Subject: SELF (SouthEast LinuxFest) RFP|