Re: WAL compression setting after PostgreSQL LZ4 default change

From: Christoph Berg <myon(at)debian(dot)org>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Japin Li <japinli(at)hotmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, wenhui qiu <qiuwenhuifx(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-07 22:58:59
Message-ID: ak2Es90xR35P2jPB@msg.df7cb.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: Jelte Fennema-Nio
> A small correction though: "on" isn't the default. The default is
> "off". So this would only impact users who changed the setting in
> their cluster to "on" at some point in the past when lz4/zstd support
> did not exist yet. So we wouldn't be changing the default. We'd be
> changing the behavior for people who changed their default setting at
> some point.

If someone just wants compression and not bother with the ugly details
of compression algorithms, they might be inclined to just say "on".
By labelling one of the choices with this "easy" value, we are
effectively promoting pglz as a good choice. (I'm definitely one of
those people, if you give me too many options, I will look for some
hint what to do or walk away. Now 3 isn't "too many" but you get the
idea.)

I would like to see "on" to be moved to some better value (likely lz4,
like toast compression), and if some day, there is yet a better
choice, we should move it again.

Christoph

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2026-07-07 23:00:32 Re: index prefetching
Previous Message Michael Paquier 2026-07-07 22:58:14 Re: Add malloc attribute to memory allocation functions