Re: WAL compression setting after PostgreSQL LZ4 default change - Mailing list pgsql-hackers

From Japin Li
Subject Re: WAL compression setting after PostgreSQL LZ4 default change
Date
Msg-id SY7PR01MB1092164C7361832D0229CEB5FB6D72@SY7PR01MB10921.ausprd01.prod.outlook.com
Whole thread
Responses Re: pg_createsubscriber: allow duplicate subscription names
List pgsql-hackers
On Sat, 01 Aug 2026 at 00:50, Christoph Berg <myon@debian.org> wrote:
> Re: Tomas Vondra
>> Thanks. FWIW I've brought this up with the RMT, and there seem to be no
>> objections to getting this done for PG19. Unless someone objects in the
>> next couple days, I'll get it committed.
>
> Thanks!
>
>> AFAIK the algorithms make different trade offs - zstd tends to compress
>> better, but uses (substantially) more CPU. I think it makes sense to
>> default to lz4, it's clearly better than pglz, with low CPU usage.
>
> Yes, lz4 makes sense to me now. zstd is the "can I tune it harder" pick.
>

How about adding a comment or documentation to clarify the rationale for
choosing lz4 over zstd?

> Christoph

-- 
Regards,
Japin Li
ChengDu WenWu Information Technology Co., Ltd.



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: add list of major features to the v19 release notes
Next
From: Masahiko Sawada
Date:
Subject: Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation