Re: BUG #14210: filter by "=" constraint doesn't work when hash index is present on a column

Peter Geoghegan <pg(at)heroku(dot)com> writes:
> On Sat, Jul 16, 2016 at 12:35 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So I just made the create_index test create and immediately drop the
>> index. We have other tests that are supposed to exercise searches of
>> hash indexes, anyway.

> I suppose that the assertion made the new hash index searches redundant.

[ thinks about it a bit more... ] Actually, maybe it doesn't. The thing
that made 9f03ca915196dfc8 really nasty is that it built an index that was
actually corrupt, with incorrect hash codes stored for entries. I think
your assertion would probably have caught that, but only accidentally,
because the problem had little to do with whether the sort satisfied its
charter. Maybe we should stick at least one simple test query in there
before we drop the index again.

regards, tom lane