From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, 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: | 2014-01-25 21:54:12 |
Message-ID: | 20140125215412.GI9750@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Uh, were are we on this? Is it a TODO?
---------------------------------------------------------------------------
On Wed, Jul 3, 2013 at 01:39:28PM +0530, Atri Sharma wrote:
> 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
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-01-25 21:56:37 | Re: A minor correction in comment in heaptuple.c |
Previous Message | Tom Lane | 2014-01-25 21:53:39 | Re: A minor correction in comment in heaptuple.c |