From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>, Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, amul sul <sulamul(at)gmail(dot)com> |
Subject: | Re: Hash Functions |
Date: | 2017-05-14 04:23:46 |
Message-ID: | CA+TgmoZJ4c=V-0O6HZ_iExRv29ZSWFmrHEJuT+Y5OOa3MKRS+g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 13, 2017 at 11:47 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> It'll be differently sized on different platforms. So everyone will have to write hash functions that look at each member individually, rather than hashing the entire struct at once. And for each member you'll have to use a type specific hash function...
Well, that's possibly kind of annoying, but it still sounds like
pretty mechanical work.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-05-14 04:48:22 | Re: Latest Data::Dumper breaks hstore_plperl regression test |
Previous Message | Robert Haas | 2017-05-14 04:11:15 | Re: Hash Functions |