Re: Do we want a hashset type? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Do we want a hashset type?
Date
Msg-id 88db5915-5105-4f2a-9155-2e218aef7c9a@dunslane.net
Whole thread Raw
In response to Re: Do we want a hashset type?  ("Joel Jacobson" <joel@compiler.org>)
Responses Re: Do we want a hashset type?
Re: Do we want a hashset type?
List pgsql-hackers
On 2023-06-16 Fr 20:38, Joel Jacobson wrote:
>
> New patch is attached, which will henceforth always be a complete patch,
> to avoid the hassle of having to assemble incremental patches.


Cool, thanks.


A couple of random thoughts:


. It might be worth sending a version number with the send function 
(c.f. jsonb_send / jsonb_recv). That way would would not be tied forever 
to some wire representation.

. I think there are some important set operations missing: most notably 
intersection, slightly less importantly asymmetric and symmetric 
difference. I have no idea how easy these would be to add, but even for 
your stated use I should have thought set intersection would be useful 
("Who is a member of both this set of friends and that set of friends?").

. While supporting int4 only is OK for now, I think we would at least 
want to support int8, and probably UUID since a number of systems I know 
of use that as an object identifier.


cheers


andrew


-- 

Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] hstore: Fix parsing on Mac OS X: isspace() is locale specific
Next
From: Tomas Vondra
Date:
Subject: Re: Use generation context to speed up tuplesorts