Re: [POC] A better way to expand hash indexes.
Mithun Cy <mithun.cy@enterprisedb.com>
From: Mithun Cy <mithun.cy@enterprisedb.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: David Steele <david@pgmasters.net>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-03-23T19:52:34Z
Lists: pgsql-hackers
Attachments
- expand_hashbucket_efficiently_04.patch (application/octet-stream) patch
Hi Amit please find the new patch On Tue, Mar 21, 2017 at 8:16 AM, Amit Kapila <amit.kapila16@gmail.com> wrote: > It is not only about above calculation, but also what the patch is > doing in function _hash_get_tbuckets(). By the way function name also > seems unclear (mainly *tbuckets* in the name). Fixed I have introduced some macros for readability and added more comments to explain why some calculations are mad. Please let me know if you think more improvements are needed. >spelling. >/forth/fourth >/at time/at a time Thanks fixed. -- Thanks and Regards Mithun C Y EnterpriseDB: http://www.enterprisedb.com
Commits
-
Fix formula in _hash_spareindex.
- b38006ef6d1b 10.0 landed
-
Expand hash indexes more gradually.
- ea69a0dead51 10.0 landed
-
Change hash indexes to store only the hash code rather than the whole indexed
- 4adc2f72a4cc 8.4.0 cited