Re: change default default_toast_compression to lz4? - Mailing list pgsql-hackers

From Jelte Fennema-Nio
Subject Re: change default default_toast_compression to lz4?
Date
Msg-id CAGECzQQgMGQ_tvH+fN1QTpaUmrsmUatZCkT13PevVDQjtL3beg@mail.gmail.com
Whole thread
In response to Re: change default default_toast_compression to lz4?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 4 Mar 2026 at 06:05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Michael Paquier <michael@paquier.xyz> writes:
> > Now, let's see how much this abreaks the buildfarm..  Because things
> > will break.  I'll send a poke to the buildfarm mailing list.
>
> I don't think this idea is really fully baked yet.  What happens
> if I build with liblz4, and run for a while with that so that
> there are lz4-compressed TOAST values, and then try to update
> to a build without LZ4?

That doesn't seem like a new problem to me. That's already possible
since PG14. To me it actually seems more likely to happen, because we
default to allowing builds without lz4 (which we stopped doing on
master). The fact that we haven't had (many) people complain indicates
to me that it isn't a big problem in practice.



pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: BUG: Former primary node might stuck when started as a standby
Next
From: Jelte Fennema-Nio
Date:
Subject: Re: Need to install liblz4-dev