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

From Rahila Syed
Subject Re: Small optimization with expanding dynamic hash table
Date
Msg-id CAH2L28vccNhRsyd1PfzdGeumKJofTh7SABA1Pmoyo_vwks=mAA@mail.gmail.com
Whole thread Raw
In response to Re: Small optimization with expanding dynamic hash table  ("cca5507" <cca5507@qq.com>)
Responses Re: Small optimization with expanding dynamic hash table
List pgsql-hackers
Hi,


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

 
Thanks for explaining, that clarifies things for me.
It may be worthwhile to check if this change has led to any performance improvements.
  
Thank you,
Rahila syed

pgsql-hackers by date:

Previous
From: Evgeny
Date:
Subject: Re: Elimination of the repetitive code at the SLRU bootstrap functions.
Next
From: Aleksander Alekseev
Date:
Subject: Re: array_random