Re: WAL compression setting after PostgreSQL LZ4 default change

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, 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>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Andres Freund <andres(at)anarazel(dot)de>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, 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-09 13:34:07
Message-ID: 9444bb52-136d-46e1-9989-ab514f127dc1@vondra.me
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Here's a v5, with mostly minor changes compared to v4.

The main change is that it prefers zstd over lz4, per the discussion
about benchmark results. This is what v3 did.

I did not like the DEFAULT_WAL_COMPRESSION name, because that seems to
imply default for the wal_compression GUC. Which is misleading. I've
renamed it to WAL_COMPRESSION_ON.

Updated/reworded the commit message a bit. Feel free to suggest
adjustments. I've included only two people as reviewers - there's been a
lot of discussion about what "on" should mean, but I don't think that
counts as reviews.

regards

--
Tomas Vondra

Attachment Content-Type Size
v5-0001-Change-wal_compression-on-to-the-first-of-zstd-lz.patch text/x-patch 6.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Burd 2026-08-09 13:37:49 Re: problems with toast.* reloptions
Previous Message Chengpeng Yan 2026-08-09 12:50:09 Re: Is there value in having optimizer stats for joins/foreignkeys?