WAL compression setting after PostgreSQL LZ4 default change

From: wenhui qiu <qiuwenhuifx(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Japin Li <japinli(at)hotmail(dot)com>, John Naylor <johncnaylorls(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: WAL compression setting after PostgreSQL LZ4 default change
Date: 2026-06-30 10:25:09
Message-ID: CAGjGUAL1b=Mwd1SCvLbo+fivEr9KDpFcu4jmqKCZXwT=6CiiGQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

HI

The recent PostgreSQL commit changes the default TOAST compression to lz4
when LZ4 support is available, based on the rationale that LZ4 is generally
more efficient than pglz in terms of CPU usage and compression ratio.Given
that, should we also consider changing the default compression method used
by wal_compression = on from pglz to lz4?

Currently, wal_compression = on still maps to pglz, while lz4 has to be
selected explicitly with:

wal_compression = lz4
If LZ4 is now considered stable and preferable enough to become the default
for TOAST compression, it may be worth aligning WAL compression behavior as
well, or at least discussing whether on should continue to imply pglz.

Thanks

Attachment Content-Type Size
v001-wal-compression-on-lz4.patch application/octet-stream 2.9 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2026-06-30 10:51:13 Re: WAL compression setting after PostgreSQL LZ4 default change
Previous Message Roman Khapov 2026-06-30 10:22:58 DROP INVALID INDEXES command