| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | Nikita Malakhov <hukutoc(at)gmail(dot)com> |
| Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 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-27 07:36:13 |
| Message-ID: | CANbhV-ED5xULjQ31kNufRWa3xiKti0TNaJGhzxn0+fRf7CCv8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 17 Jul 2022 at 19:15, Nikita Malakhov <hukutoc(at)gmail(dot)com> wrote:
> we suggest that as an improvement compression should be put inside the Toaster as an option,
> thus the Toaster could have maximum benefits from knowledge of data internal structure (and in future use JSON Schema).
Very much agreed.
> For using in special Toaster for JSON datatype compression dictionaries seem to be very valuable addition, but now I
> have to agree that this feature in current state is competing with Pluggable TOAST.
But I don't understand this.
Why does storing a compression dictionary in the catalog prevent that
dictionary from being used within the toaster?
--
Simon Riggs http://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2022-07-27 07:54:07 | Re: making relfilenodes 56 bits |
| Previous Message | Matthias van de Meent | 2022-07-27 07:35:24 | Re: Improving btree performance through specializing by key shape, take 2 |