Re: PGLZ Compression Optimization

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PGLZ Compression Optimization
Date: 2026-07-16 14:00:22
Message-ID: f7ac9cb5-c33d-47df-8f00-72df35a90a39@vondra.me
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 7/16/26 11:08, wenhui qiu wrote:
> Hi Tomas
>
> Thank you for your reply , Why did I come up with this idea? When I
> suggested changing `wal_compression on` to  ZSTD or LZ4,  Wasn’t
> accepted. So I wondered if it could be implemented internally. In
> any case, it can’t compete with LZ4, so I don’t think it’s worth
> investing effort into improving PG-LZ. Setting LZ4 or ZSTD as the
> default is the best option.
>

Maybe I'm missing something, but I did check the wal_compression thread
[1], and I don't think it was rejected at all. I think people agree with
the proposa to change what 'on' means, depending on whether lz4/zstd is
supported by the build. And I agree with that plan, so let me comment on
that thread.

[1]
https://www.postgresql.org/message-id/flat/CAGjGUAL1b%3DMwd1SCvLbo%2BfivEr9KDpFcu4jmqKCZXwT%3D6CiiGQ%40mail.gmail.com

--
Tomas Vondra

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2026-07-16 14:06:42 Re: PGLZ Compression Optimization
Previous Message Xing Guo 2026-07-16 13:52:38 Re: [PATCH v1] plpython: Pair SPI_connect and SPI_finish in the same function