On Mon, Jun 12, 2023, at 22:36, Joel Jacobson wrote: > On Mon, Jun 12, 2023, at 21:58, Tomas Vondra wrote: >> My suggestion is to be lazy, just use the lookup3 we have in hashfn.c >> (through hash_bytes or something), and at the same time make it possible >> to switch to a different function in the future. I'd store and ID of the >> hash function in the set, so that we can support a different algorithm >> in the future, if we choose to.
hashset is now using hash_bytes_uint32() from hashfn.h Other changes in the same commit: * Introduce hashfn_id field to specify hash function ID * Implement hashset_send and hashset_recv and add C-test using libpq * Add operators and operator classes for hashset comparison, sorting and distinct queries Looks good? If so, I wonder what's best to focus on next? Perhaps adding support for bigint? Other ideas? /Joel
hashset-0.0.1-da3b024.patch
Description: Binary data
