From: | Tommy Pavlicek <tommypav122(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | [PATCH] ltree hash functions |
Date: | 2023-06-17 15:45:10 |
Message-ID: | CAEhP-W9ZEoHeaP_nKnPCVd_o1c3BAUvq1gWHrq8EbkNRiS9CvQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi All,
I've written a patch to add hash functions for the ltree extension. It adds
support for hash indexes and hash aggregation. I've reused the existing
logic that's used to hash arrays and added tests that mirror elsewhere
(i.e. hstore and hash_func regression tests).
The patch doesn't currently support hash joins as the ltree = operator was
created without support for it. The ALTER OPERATOR command doesn't support
changing the hash join support, so I'm not sure what the best strategy to
change it is. Is it ok to update the operator's row in the pg_operator
system catalog or is there a better way to change this that someone could
recommend?
Any comments on the overall approach or other feedback would be appreciated.
Thanks,
Tommy
Attachment | Content-Type | Size |
---|---|---|
ltree-hash-v1.patch | application/octet-stream | 9.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Gurjeet Singh | 2023-06-17 16:09:02 | Re: [17] CREATE COLLATION default provider |
Previous Message | Evan Jones | 2023-06-17 14:57:05 | Re: [PATCH] hstore: Fix parsing on Mac OS X: isspace() is locale specific |