Re: WAL compression setting after PostgreSQL LZ4 default change

From: Christoph Berg <myon(at)debian(dot)org>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: 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:10:29
Message-ID: amyexT2WCaoCBc7G@msg.df7cb.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: Tomas Vondra
> 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.

About the intent, I see it more as "PG19 is the version that switched
away from pglz". It could be lz4 for both, or it could be lz4 for
TOAST and zstd for WAL.

There is some value in having both the same, but I'd defer to what the
others are saying.

I don't have a preference either way. This was just the last thing
expressed here. (If we can't agree on that point, could we please
still make the change and just toss a coin about this "bit"? :D)

Christoph

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bohyun Lee 2026-07-31 13:13:55 [Patch]The Case For WAL-Logging pg_upgrade
Previous Message Tomas Vondra 2026-07-31 13:04:03 Re: WAL compression setting after PostgreSQL LZ4 default change