Re: hash index improving v3 - Mailing list pgsql-patches

From Alex Hunsaker
Subject Re: hash index improving v3
Date
Msg-id 34d269d40809051321w2ed16037od0373a4a29c311f1@mail.gmail.com
Whole thread Raw
In response to Re: hash index improving v3  ("Alex Hunsaker" <badalex@gmail.com>)
Responses Re: hash index improving v3  ("Alex Hunsaker" <badalex@gmail.com>)
Re: hash index improving v3  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
List pgsql-patches
Ok now that I made it so it actually *test* collisions, with the patch
it always returns all rows that matched the hashed "key".  For example
(non lobotomized inthash8, I just brute forced some collisions for 0
so that anyone can try this)

create table test_hash (num int8);
insert into test_hash (num) values (0), (1805671691), (3294821164),
(4294967297);
create index test_hash_num_idx on test_hash using hash (num);
select * from test_hash where num = 0;
    num
------------
          0
 1805671691
 3294821164
 4294967297

set enable_bitmapscan to off;

select * from test_hash where num = 0;
 num
-----
   0

CVS HEAD, 8_3_STABLE obviously work if I force the index scan

pgsql-patches by date:

Previous
From: "David Rowley"
Date:
Subject: Re: [HACKERS] TODO item: Implement Boyer-Moore searching (First time hacker)
Next
From: "David Rowley"
Date:
Subject: Re: libpq events patch (with sgml docs)