From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
Subject: | Re: [PATCH] Compression dictionaries for JSONB |
Date: | 2022-07-11 14:44:42 |
Message-ID: | CAJ7c6TMJpvGER4qaK__20BbzGKw5Z=twOKxPgemSV97T4eSmpQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi hackers,
> OK, I see your point now. And I think this is a very good point.
> Basing "Compression dictionaries" on the API provided by "pluggable
> TOASTer" can also be less hacky than what I'm currently doing with
> `typmod` argument. I'm going to switch the implementation at some
> point, unless anyone will object to the idea.
Here is the rebased patch. I reworked the memory management a bit but
other than that there are no new changes.
So far we seem to have a consensus to:
1. Use bytea instead of NameData to store dictionary entries;
2. Assign monotonically ascending IDs to the entries instead of using
Oids, as it is done with pg_class.relnatts. In order to do this we
should either add a corresponding column to pg_type, or add a new
catalog table, e.g. pg_dict_meta. Personally I don't have a strong
opinion on what is better. Thoughts?
Both changes should be straightforward to implement and also are a
good exercise to newcomers.
I invite anyone interested to join this effort as a co-author! (since,
honestly, rewriting the same feature over and over again alone is
quite boring :D).
--
Best regards,
Aleksander Alekseev
Attachment | Content-Type | Size |
---|---|---|
v4-0001-Compression-dictionaries-for-JSONB.patch | application/octet-stream | 49.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-07-11 15:37:39 | Re: automatically generating node support functions |
Previous Message | Sergey Dudoladov | 2022-07-11 14:43:12 | Re: Add connection active, idle time to pg_stat_activity |