Re: [PERFORM] BUG #2737: hash indexing large tablefails,while - Mailing list pgsql-bugs

From Julius.Stroffek
Subject Re: [PERFORM] BUG #2737: hash indexing large tablefails,while
Date
Msg-id 455DD6F2.9070009@Sun.COM
Whole thread Raw
In response to Re: [PERFORM] BUG #2737: hash indexing large tablefails,while btree of same index works  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-bugs
Simon Riggs wrote:
> Do we think there is hope of improving hash indexes?
I thought about this a bit. I have an idea that the hash index might
have the fixed number of buckets specified in create index statement and
the tuples in each of these buckets should be stored in a b-tree. This
should give a constant performance improvement (but based on the number
of buckets) for each fetch of a tuple from index compared to a fetch
from b-tree index.

cheers

Julo



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PERFORM] BUG #2737: hash indexing large tablefails,while btree of same index works
Next
From: "Thomas H."
Date:
Subject: Re: xlog lockup patch (was: BUG #2712: could not fsync segment: Permission)