| From: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(at)vondra(dot)me>, Christoph Berg <myon(at)debian(dot)org>, 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-20 06:23:59 |
| Message-ID: | CAGjGUA+ERbxcGzfiKDT2LpqU095E5=E2BvqCWXMTKgm-jns14Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
HI
> > A few releases later, where I know that many deployments are using
> > either lz4 or zstd and nobody has complained back, I see a much better
> > argument in changing the behavior of "on" to mean "zstd" -> "lz4" ->
> > "pglz" in order of priority, based on how efficient these algorithms
> > are known to be.
>
> V2 path does exactly that.
>
> > It would be compelling to make this change for v19, so that it is in line
> > with the change for "default_toast_compression". But I guess it is too
> late
> > in the cycle for that.
>
> The feature was frozen in April. It won't be too late to include it in
> Version 20—better late than never.
>
>
Thanks
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2026-07-20 06:41:31 | Re: sequencesync worker race with REFRESH SEQUENCES |
| Previous Message | lakshmi | 2026-07-20 05:52:52 | Re: let ALTER TABLE DROP COLUMN drop whole-row referenced object |