Re: Small optimization with expanding dynamic hash table - Mailing list pgsql-hackers

From cca5507
Subject Re: Small optimization with expanding dynamic hash table
Date
Msg-id tencent_2B0E56ED38430B0B716AE5537E6436F02A09@qq.com
Whole thread Raw
Responses Re: Small optimization with expanding dynamic hash table
List pgsql-hackers
> Will this still work if new_bucket is not equal to hctl->low_mask + 1?
Yes, for example:

low_mask: 0x011, high_mask: 0x111, old_bucket: 0x010, new_bucket: 0x110

The old_bucket's hash value like 0x***010 or 0x***110, the later is in the old_bucket is because we didn't have new_bucket before, so only hash value like 0x***110 needs relocation: hashvalue & (low_mask + 1) != 0

--
Regards,
ChangAo Chen

pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: support create index on virtual generated column.
Next
From: Michael Paquier
Date:
Subject: Re: Support for 8-byte TOAST values (aka the TOAST infinite loop problem)