Re: pglz compression performance, take two
От | Tomas Vondra |
---|---|
Тема | Re: pglz compression performance, take two |
Дата | |
Msg-id | 0f54129f-255d-2d8f-94a0-d18b6f388745@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: pglz compression performance, take two (Andrey Borodin <amborodin86@gmail.com>) |
Ответы |
Re: pglz compression performance, take two
|
Список | 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 по дате отправления: