Re: Why hash indexes suck - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: Why hash indexes suck
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA40184D0F6@m0114.s-mxs.net
Whole thread Raw
In response to Why hash indexes suck  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Why hash indexes suck
List pgsql-hackers
> We could safely sort on the hash value, but I'm not sure how effective
> that would be, considering that we're talking about values that already
> hashed into the same bucket --- there's likely not to be very many
> distinct hash values there.

I think we can safely put that on the todo list.
The existing hash algorithm is very good. So I would on the
contrary beleive that only a few keys share a hash value per pagesized bucket.
For the equal keys case it does not matter since we want all of the rows anyways.
For the equal hash value case it would probably be best to sort by ctid.

TODO ?: order heap pointers inside hash index pages by hash value and ctid

Andreas


pgsql-hackers by date:

Previous
From: jihuang
Date:
Subject: Re: CREATE DATABASE on the heap with PostgreSQL?
Next
From: Gaetano Mendola
Date:
Subject: Re: CREATE DATABASE on the heap with PostgreSQL?