| From: | Andrey Borodin <amborodin86(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pglz compression performance, take two |
| Date: | 2023-02-05 18:36:39 |
| Message-ID: | CAAhFRxhCMG4b17SdheURdEF2AdByUXnrokqLV9Cas9qmKq7aJQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 6, 2023 at 10:02 PM Andrey Borodin <amborodin86(at)gmail(dot)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 | Content-Type | Size |
|---|---|---|
| v9-0001-Reorganize-pglz-compression-code.patch | application/octet-stream | 20.2 KB |
| v9-0002-Fix-oversight-for-compression-of-last-4-bytes.patch | application/octet-stream | 969 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-02-05 19:06:02 | Re: [PATCH] Compression dictionaries for JSONB |
| Previous Message | Albin Hermange | 2023-02-05 18:16:04 | add a "status" column to the pg_rules system view |