| From: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A better way than tweaking NTUP_PER_BUCKET |
| Date: | 2013-07-03 08:09:28 |
| Message-ID: | CAOeZVif_hbmZ0yThvqwR=SoDrnedVE=jqjX209NqrTUFraikyg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all,
I have been working on a patch for the above discussed
functionalities. I made an array of int32s, one for each bucket in a
hash table(the array is per hash table).
I am using the hash value directly to set the corresponding bit in the
bit field.Specifically:
bitfield_orvalue = 1<<hashvalue;
hashtable->bitFields[bucketNumber] =
(hashtable->bitFields[bucketNumber]) |bitfield_orvalue;
But,the hash values are way beyond this, and I admit that my choice of
int32 as bitfield isn't correct here.
The hash values are like:
1359910425
1359910425
-1662820951
-1662820951
What should I be using for the bit map?
Regards,
Atri
--
Regards,
Atri
l'apprenant
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2013-07-03 08:12:50 | Re: [PATCH] Add an ldapoption to disable chasing LDAP referrals |
| Previous Message | Kyotaro HORIGUCHI | 2013-07-03 07:51:22 | Re: Reduce maximum error in tuples estimation after vacuum. |