From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Joel Jacobson <joel(at)compiler(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Do we want a hashset type? |
Date: | 2023-06-11 14:58:41 |
Message-ID: | 5e796ab9-1182-768c-d31e-2bbfc2859e73@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2023-06-11 Su 06:26, Joel Jacobson wrote:
> On Sat, Jun 10, 2023, at 22:26, Tomas Vondra wrote:
>> On 6/10/23 17:46, Andrew Dunstan wrote:
>>> Maybe you can post a full patch as well as incremental?
>>>
>> I wonder if we should keep discussing this extension here, considering
>> it's going to be out of core (at least for now). Not sure how many
>> pgsql-hackers are interested in this, so maybe we should just move it to
>> github PRs or something ...
> I think there are some good arguments that speaks in favour of including it in core:
>
> 1. It's a fundamental data structure.
That's reason enough IMNSHO.
> Perhaps "set" would have been a better name,
> since the use of hash functions from an end-user perspective is implementation
> details, but we cannot use that word since it's a reserved keyword, hence "hashset".
Rather than use "hashset", which as you say is based on an
implementation detail, I would prefer something like "integer_set" -
what it's a set of.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2023-06-11 15:03:04 | Re: Do we want a hashset type? |
Previous Message | Tomas Vondra | 2023-06-11 12:41:27 | Should heapam_estimate_rel_size consider fillfactor? |