Re: pglz compression performance, take two - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: pglz compression performance, take two
Date
Msg-id 0f54129f-255d-2d8f-94a0-d18b6f388745@enterprisedb.com
Whole thread Raw
In response to Re: pglz compression performance, take two  (Andrey Borodin <amborodin86@gmail.com>)
Responses Re: pglz compression performance, take two
List pgsql-hackers
On 2/5/23 19:36, Andrey Borodin wrote:
> On Fri, Jan 6, 2023 at 10:02 PM Andrey Borodin <amborodin86@gmail.com> wrote:
>>
>> Hello! Please find attached v8.
> 
> I got some interesting feedback from some patch users.
> There was an oversight that frequently yielded results that are 1,2 or
> 3 bytes longer than expected.
> Looking closer I found that the correctness of the last 3-byte tail is
> checked in two places. PFA fix for this. Previously compressed data
> was correct, however in some cases few bytes longer than the result of
> current pglz implementation.
> 

Thanks. What were the consequences of the issue? Lower compression
ratio, or did we then fail to decompress the data (or would current pglz
implementation fail to decompress it)?


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Yuya Watari
Date:
Subject: Re: [PoC] Reducing planning time when tables have many partitions
Next
From: Andrey Borodin
Date:
Subject: Re: pglz compression performance, take two