> 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.
