Request a Demo
Home   >   mailing lists

Re: WAL compression setting after PostgreSQL LZ4 default change - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: WAL compression setting after PostgreSQL LZ4 default change
Date
Msg-id CAHGQGwGv8FLvOkTm3dpTsvt70puYpzKOmq3-YQSOpDCdZ8gyaQ@mail.gmail.com
Whole thread
In response to Re: WAL compression setting after PostgreSQL LZ4 default change  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
On Wed, Jul 1, 2026 at 8:45 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Tue, Jun 30, 2026 at 06:25:09PM +0800, wenhui qiu wrote:
> > 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?
>
> "on" is just a backward-compatible value, so we could let it as-is.

Yes, so +1 to leaving "on" as it is. Making its meaning depend on
the build options seems very confusing. Users who want lz4 or zstd
can simply specify those methods explicitly instead of using "on".

Regards,

--
Fujii Masao

pgsql-hackers by date:

Previous
From: Ewan Young
Date:
Subject: Re: JSON_VALUE/JSON_TABLE DEFAULT expression ignores RETURNING typmod
Next
From: Michael Paquier
Date:
Subject: Re: GetBufferDescriptor() being called for local buffers from MarkBufferDirtyHint()