| From: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | John Naylor <johncnaylorls(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Document wal_compression=on |
| Date: | 2026-06-30 09:27:40 |
| Message-ID: | CAGjGUAJr6txwgZ9jC90onH4Gj5OzHHpd0w=B-JYfs+J2kXvL3w@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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2026-06-30 09:48:53 | Re: [PATCH] Document wal_compression=on |
| Previous Message | Richard Guo | 2026-06-30 09:22:15 | Re: Fix HAVING-to-WHERE pushdown with mismatched operator families |