Horton

Re: ZStandard (with dictionaries) compression support for TOAST compression

Nikita Malakhov <hukutoc@gmail.com>

View thread
From: Nikita Malakhov <hukutoc@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Nikhil Kumar Veldanda <veldanda.nikhilkumar17@gmail.com>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org
Date: 2025-05-07T08:40:14Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Split regression tests for TOAST compression methods into two files

  2. Refactor non-supported compression error message in toast_compression.c

Hi!

Michael, what do you think of this approach (extending varatt_external)
vs extending varatt itself by new tag and structure? The second approach
allows more flexibility, independence of existing structure without
modifying
varatt_4b and is extensible further. I mentioned it above (extending
the TOAST pointer), and it could be implemented more easily and in a less
confusing way.

I'm +1 on storing dictionary somewhere around actual data (not necessary
in the data storage area itself) but strongly against new catalog table
with dictionaries - it involves a lot of side effects, including locks
while working
with this table resulting in performance degradation, and so on.

>
> --
Regards,
Nikita Malakhov
Postgres Professional
The Russian Postgres Company
https://postgrespro.ru/