Re: Hash indexes (was: On-disk bitmap index patch)

From: "Luke Lonergan" <llonergan(at)greenplum(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Skype Technologies OY" <hannu(at)skype(dot)net>, mark(at)mark(dot)mielke(dot)cc, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Jie Zhang" <jzhang(at)greenplum(dot)com>, "Gavin Sherry" <swm(at)linuxworld(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Hash indexes (was: On-disk bitmap index patch)
Date: 2006-08-01 14:55:35
Message-ID: C0F4B977.2B728%llonergan@greenplum.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim,

On 7/28/06 12:27 PM, "Jim C. Nasby" <jnasby(at)pervasive(dot)com> wrote:

> In that case, perhaps this is something Greenplum might be interested
> in, since it might fit nicely between bitmap and btree indexes.

I'm certainly following the thread.

We have talked about hash and btree organized tables both here, but haven't
gotten far enough along to evaluate what's already there in pg.

Looks like this thread has nicely characterized the problems with what's
there.

WRT hashing - we use FNV hash which is a very nice, very fast modern hash
algorithm. We would contribute that if we worked on this.

- Luke

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-08-01 14:57:29 Re: [HACKERS] float8 regression failure (HEAD, cygwin)
Previous Message Andrew Dunstan 2006-08-01 14:54:10 Re: Hash indexes