Re: Hash indexes (was: On-disk bitmap index patch) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Hash indexes (was: On-disk bitmap index patch)
Date
Msg-id 20060727174601.GE18774@surnet.cl
Whole thread Raw
In response to Hash indexes (was: On-disk bitmap index patch)  (Jim Nasby <jnasby@pervasive.com>)
Responses Re: Hash indexes (was: On-disk bitmap index patch)  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
Jim Nasby wrote:
> On Jul 25, 2006, at 3:31 PM, Tom Lane wrote:
> >Hannu Krosing <hannu@skype.net> writes:

> >>What would be the use-case for hash indexes ? And what should be
> >>done to make them faster than btree ?
> >
> >If we knew, we'd do it ;-)  But no one's put enough effort into it
> >to find out.
> 
> Do they use the same hash algorithm as hash joins/aggregation? If so,  
> wouldn't hash indexes be faster for those operations than regular  
> indexes?

The main problem doesn't seem to be in the hash algorithm (which I
understand to mean the hashing function), but in the protocol for
concurrent access of index pages, and the distribution of keys in pages
of a single hash key.

This is described in a README file or a code comment somewhere in the
hash AM code.  Someone needs to do some profiling to find out what the
bottleneck really is, and ideally find a way to fix it.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: lastval exposes information that currval does not
Next
From: "Bort, Paul"
Date:
Subject: Re: GUC with units, details