Re: [HACKERS] Custom compression methods - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: [HACKERS] Custom compression methods
Date
Msg-id 376CC7A5-969C-4A53-8597-C736BEFBF7F7@yandex-team.ru
Whole thread Raw
In response to Re: [HACKERS] Custom compression methods  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: [HACKERS] Custom compression methods
List pgsql-hackers

> 28 дек. 2020 г., в 10:20, Dilip Kumar <dilipbalaut@gmail.com> написал(а):
>
> On Sun, Dec 27, 2020 at 12:40 PM Andrey Borodin <x4mmm@yandex-team.ru> wrote:
>>
>>
>>
>>> 25 дек. 2020 г., в 14:34, Dilip Kumar <dilipbalaut@gmail.com> написал(а):
>>>
>>> <v16-0002-alter-table-set-compression.patch> <v16-0004-Create-custom-compression-methods.patch>
<v16-0005-new-compression-method-extension-for-zlib.patch><v16-0001-Built-in-compression-method.patch>
<v16-0003-Add-support-for-PRESERVE.patch><v16-0006-Support-compression-methods-options.patch> 
>>
>> Maybe add Lz4\Zlib WAL FPI compression on top of this patchset? I'm not insisting on anything, it just would be so
coolto have it... 
>>
>> BTW currently there are Oid collisions in original patchset.
>
> Thanks for the patch.  Maybe we can allow setting custom compression
> methods for wal compression as well.

No, unfortunately, we can't use truly custom methods. Custom compression handlers are WAL-logged. So we can use only
staticset of hardcoded compression methods. 

Thanks!

Best regards, Andrey Borodin.


pgsql-hackers by date:

Previous
From: vignesh C
Date:
Subject: Re: Parallel Inserts in CREATE TABLE AS
Next
From: Masahiko Sawada
Date:
Subject: Re: New IndexAM API controlling index vacuum strategies