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

From Andrey Borodin
Subject Re: pglz compression performance, take two
Date
Msg-id CAAhFRxhCMG4b17SdheURdEF2AdByUXnrokqLV9Cas9qmKq7aJQ@mail.gmail.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
Re: pglz compression performance, take two
List pgsql-hackers
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!

Best regards, Andrey Borodin.

Attachment

pgsql-hackers by date:

Previous
From: Albin Hermange
Date:
Subject: add a "status" column to the pg_rules system view
Next
From: Andres Freund
Date:
Subject: Re: [PATCH] Compression dictionaries for JSONB