From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: inet type/merge joins |
Date: | 2001-06-10 16:42:19 |
Message-ID: | 21067.992191339@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alex Pilosov <alex(at)pilosoft(dot)com> writes:
>> At some point it'd be nice to use type-specific hash functions for
>> hashjoin --- we support 'em for hash indexes, and I don't see why the
>> join mechanism should not use the same functions. With that, it'd be
>> possible to overcome this problem by making a hash function that has
>> the same blind spots as the comparison function ...
> I guess the idea is to add a hash function to a catalog of a type
> definition is a good idea?
Either that, or replace the oprcanhash boolean field of pg_operator
by an OID field that links to the appropriate hash function. Not sure
offhand which is better.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Pilosov | 2001-06-10 16:44:51 | Re: inet type/merge joins |
Previous Message | Tom Lane | 2001-06-10 16:26:44 | Re: inet type/merge joins |