| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Tom Dunstan <pgsql(at)tomd(dot)cc> |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Do we want a hashset type? |
| Date: | 2023-06-14 14:38:19 |
| Message-ID: | b2c15c63-282b-10ca-1268-3ccd2db83567@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-06-14 We 05:44, Tomas Vondra wrote:
>
> The thing is, adding stuff to core is not free - it means the community
> becomes responsible for maintenance, testing, fixing issues, etc. It's
> not feasible (or desirable) to have all extensions in core, and cloud
> vendors generally do have ways to support some pre-vetted extensions
> that they deem useful enough. Granted, it means vetting/maintenance for
> them, but that's kinda the point of managed services. And it'd not be
> free for us either.
I agree it's a judgement call. But the code burden here seems pretty
small, far smaller than, say, the SQL/JSON patches. And I think the
range of applications that could benefit is quite significant.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tristan Partin | 2023-06-14 14:41:14 | Re: Use COPY for populating all pgbench tables |
| Previous Message | Japin Li | 2023-06-14 13:42:37 | Re: Replace (GUC_UNIT_MEMORY | GUC_UNIT_TIME) with GUC_UNIT in guc.c |