Re: WAL compression setting after PostgreSQL LZ4 default change

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: 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>, 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-07-31 13:04:03
Message-ID: e160948f-c272-4afb-8109-d82b06e52d11@vondra.me
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 7/31/26 14:35, Christoph Berg wrote:
> I still hope that we can make the switch for PG 19 so we don't have
> two different versions flipping the toast and wal compression
> algorithms.
>

Yeah. I wonder if it's too late for that, but perhaps not. I wouldn't
mind committing it, it's not a huge/complex patch. But RMT should
probably have a say in this.

> Attached is v3 of wenhui's patch with some editorial changes in the
> documentation and a commit message.
>

The one thing I don't quite like on the patch is that it actually
defaults to zstd before lz4. Which seems to not quite match the intent
to have both toast and wal default to the same thing. I don't have a
strong preference for either algorithm, but I also don't see why to put
zstd before lz4. I'd do it the other way around, i.e. lz4->zstd->pglz.

regards

--
Tomas Vondra

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2026-07-31 13:10:29 Re: WAL compression setting after PostgreSQL LZ4 default change
Previous Message Tomas Vondra 2026-07-31 12:55:56 Re: WAL compression setting after PostgreSQL LZ4 default change