Re: WAL compression setting after PostgreSQL LZ4 default change

From: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: Ken Marshall <ktm(at)rice(dot)edu>, Hannu Krosing <hannuk(at)google(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, Christoph Berg <myon(at)debian(dot)org>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Andres Freund <andres(at)anarazel(dot)de>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Michael Paquier <michael(at)paquier(dot)xyz>, Japin Li <japinli(at)hotmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, John Naylor <johncnaylorls(at)gmail(dot)com>
Subject: Re: WAL compression setting after PostgreSQL LZ4 default change
Date: 2026-08-07 07:15:19
Message-ID: CAGjGUA+rT0OczFZFSX0qgnfwbxWhzva+xKOQQzqj4e3KtjTkmg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

> Based on this, I agree with the original suggestion to default to
> > zstd > lz4 > pglz
> > I don't think we need to "tune" the compression levels for either of the
> > algorithms. The defaults seem pretty reasonable.
>
> Thank you for your test , It looks like Michael Paquier's suggestion was
> right—zstd doesn't have much difference in CPU consumption at default
> compression levels, and it achieves a higher compression ratio. On another
> note, I recall there was a patch discussing zstd compression for TOAST, but
> it hasn't been active for a long time. Since zstd offers a higher
> compression ratio, I think it's worth pushing this forward.
>

Thanks

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nazir Bilal Yavuz 2026-08-07 07:45:54 Re: Credits For v19
Previous Message Peter Smith 2026-08-07 07:03:38 Re: pg_createsubscriber: allow duplicate subscription names