On 11/16/07, Alex Vinokur <[EMAIL PROTECTED]> wrote:
> I would like to use both hashlittle() and hashword() (or
> hashword_little) on little-endian and big-endian machine and to get
> identical hashValues.
Whats wrong with hashlittle()? It does use the same optimized
reading on LE platform that h
On Fri, Nov 16, 2007 at 01:19:13AM -0800, Alex Vinokur wrote:
> On Nov 15, 1:23 pm, [EMAIL PROTECTED] (Heikki Linnakangas)
> wrote:
> > Alex Vinokurwrote:
> > > On Nov 15, 10:40 am,Alex Vinokur<[EMAIL PROTECTED]>
> > > wrote:
> > > [snip]
> > >> I have some question concerning Bob Jenkins' function
On Nov 15, 1:23 pm, [EMAIL PROTECTED] (Heikki Linnakangas)
wrote:
> Alex Vinokurwrote:
> > On Nov 15, 10:40 am,Alex Vinokur<[EMAIL PROTECTED]>
> > wrote:
> > [snip]
> >> I have some question concerning Bob Jenkins' functions
> >> hashword(uint32_t*, size_t), hashlittle(uint8_t*, size_t) and
> >> ha
On Nov 15, 10:40 am, Alex Vinokur <[EMAIL PROTECTED]>
wrote:
[snip]
> I have some question concerning Bob Jenkins' functions
> hashword(uint32_t*, size_t), hashlittle(uint8_t*, size_t) and
> hashbig(uint8_t*, size_t) in lookup3.c.
>
> Let k1 by a key: uint8_t* k1; strlen(k1)%sizeof(uint32_t) == 0.
Alex Vinokur wrote:
On Nov 15, 10:40 am, Alex Vinokur <[EMAIL PROTECTED]>
wrote:
[snip]
I have some question concerning Bob Jenkins' functions
hashword(uint32_t*, size_t), hashlittle(uint8_t*, size_t) and
hashbig(uint8_t*, size_t) in lookup3.c.
Let k1 by a key: uint8_t* k1; strlen(k1)%sizeof(ui
On Oct 27, 10:15 pm, [EMAIL PROTECTED] (Kenneth Marshall) wrote:
> Dear PostgreSQL Developers,
>
> This patch is a "diff -c" against the hashfunc.c from postgresql-8.3beta1.
> It implements the 2006 version of the hash function by Bob Jenkins. Its
> features include a better and faster hash functio
