| From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Do we want a hashset type? |
| Date: | 2023-06-13 20:23:57 |
| Message-ID: | c4cf2b24-4eda-439f-9141-f17bf9902a7a@app.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 13, 2023, at 20:50, Joel Jacobson wrote:
> hashset is now using hash_bytes_uint32() from hashfn.h
I spotted a problem in the ordering logic of the comparison functions.
The issue was with handling hashsets containing empty positions,
causing non-lexicographic ordering.
The updated implementation now correctly iterates over the hashsets,
skipping any empty positions, which results in proper comparison
and ordering of elements present in the hashset.
New patch attached.
| Attachment | Content-Type | Size |
|---|---|---|
| hashset-4e60615.patch | application/octet-stream | 9.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-06-13 20:28:31 | Re: Document that server will start even if it's unable to open some TCP/IP ports |
| Previous Message | Tom Lane | 2023-06-13 20:23:24 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |