Re: [HACKERS] Custom compression methods
Dilip Kumar <dilipbalaut@gmail.com>
Attachments
- v23-0003-Add-support-for-PRESERVE.patch (text/x-patch) patch v23-0003
- v23-0004-Create-custom-compression-methods.patch (text/x-patch) patch v23-0004
- v23-0001-Built-in-compression-method.patch (text/x-patch) patch v23-0001
- v23-0002-alter-table-set-compression.patch (text/x-patch) patch v23-0002
- v23-0005-new-compression-method-extension-for-zlib.patch (text/x-patch) patch v23-0005
- v23-0006-Support-compression-methods-options.patch (text/x-patch) patch v23-0006
On Tue, Feb 9, 2021 at 6:14 PM Dilip Kumar <dilipbalaut@gmail.com> wrote: > > > Basically, we are just checking whether the stored value is compressed > > or not, but we are clearly ignoring the fact that it might be > > compressed and stored externally on disk. So basically if the value > > is stored externally we can not know whether the external data were > > compressed or not without fetching the values from the toast table, I > > think instead of fetching the complete data from toast we can just > > fetch the header using 'toast_fetch_datum_slice'. > > > > Any other thoughts on this? > > I think I was partially wrong here. Basically, there is a way to know > whether the external data are compressed or not using > VARATT_EXTERNAL_IS_COMPRESSED macro. However, if it is compressed > then we will have to fetch the toast slice of size > toast_compress_header, to know the compression method. I have fixed this issue, so now we will be able to detect the compression method of the externalized compressed data as well. I have also added a test case for this. I have rebased other patches also on top of this patch. I have fixed the doc compilation issue in patch 0004 raised by Justin. I still could not figure out what is the right place for inheriting the compression method related change in the "ddl.sgml" so that is still there, any suggestions on that? -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
Commits
-
docs: Update TOAST storage docs for configurable compression.
- e8c435a824e1 14.0 landed
-
Further tweaking of pg_dump's handling of default_toast_compression.
- 54bb91c30e39 14.0 landed
-
Fix interaction of TOAST compression with expression indexes.
- 5db1fd7823a1 14.0 landed
-
Tidy up more loose ends related to configurable TOAST compression.
- e5595de03ec6 14.0 landed
-
Short-circuit slice requests that are for more than the object's size.
- 063dd37ebc76 14.0 landed
-
Mostly-cosmetic adjustments of TOAST-related macros.
- aeb1631ed207 14.0 landed
-
Remove useless configure probe for <lz4/lz4.h>.
- 2c75f8a612b2 14.0 landed
-
Error on invalid TOAST compression in CREATE or ALTER TABLE.
- a4d5284a10b5 14.0 landed
-
docs: Fix omissions related to configurable TOAST compression.
- 24f0e395ac58 14.0 landed
-
More code cleanup for configurable TOAST compression.
- 226e2be3876d 14.0 landed
-
Bring configure support for LZ4 up to snuff.
- 4d399a6fbeb7 14.0 landed
-
Make compression.sql regression test independent of default.
- fd1ac9a54896 14.0 landed
-
Use valid compression method in brin_form_tuple
- 882b2cdc08c4 14.0 landed
-
Fix up pg_dump's handling of per-attribute compression options.
- aa25d1089ac0 14.0 landed
-
Allow configurable LZ4 TOAST compression.
- bbe0a81db69b 14.0 landed
-
Fix inconsistencies in the code
- 6b8548964bcc 13.0 cited
-
Mostly-cosmetic improvements in memory chunk header alignment coding.
- f65d21b25808 11.0 cited
-
Allow numeric to use a more compact, 2-byte header in many cases.
- 145343534c15 9.1.0 cited