| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Japin Li <japinli(at)hotmail(dot)com>, John Naylor <johncnaylorls(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org> |
| Subject: | Re: WAL compression setting after PostgreSQL LZ4 default change |
| Date: | 2026-07-03 02:58:52 |
| Message-ID: | CAHGQGwGv8FLvOkTm3dpTsvt70puYpzKOmq3-YQSOpDCdZ8gyaQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 1, 2026 at 8:45 AM Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-07-03 03:07:21 | Re: GetBufferDescriptor() being called for local buffers from MarkBufferDirtyHint() |
| Previous Message | Ashutosh Bapat | 2026-07-03 02:47:22 | Re: GetBufferDescriptor() being called for local buffers from MarkBufferDirtyHint() |