From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
---|---|
To: | "Tomas Vondra" <tomas(dot)vondra(at)enterprisedb(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "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 20:15:37 |
Message-ID: | f8020997-3b80-4f47-b69e-441eeb715f45@app.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jun 11, 2023, at 17:03, Tomas Vondra wrote:
> On 6/11/23 12:26, Joel Jacobson wrote:
>> I think there are some good arguments that speaks in favour of including it in core:
...
>
> I agree with all of that, but ...
>
> It's just past feature freeze, so the earliest release this could appear
> in is 17, about 15 months away.
>
> Once stuff gets added to core, it's tied to the release cycle, so no new
> features in between.
>
> Presumably people would like to use the extension in the release they
> already use, without backporting.
>
> Postgres is extensible for a reason, exactly so that we don't need to
> have everything in core.
Interesting, I've never thought about this one before:
What if something is deemed to be fundamental and therefore qualify for core inclusion,
and at the same time is suitable to be made an extension.
Would it be possible to ship such extension as pre-installed?
What was the json/jsonb story, was it ever an extension before
being included in core?
/Joel
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2023-06-11 22:15:15 | Re: check_strxfrm_bug() |
Previous Message | Joel Jacobson | 2023-06-11 20:05:39 | Re: Do we want a hashset type? |