| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Euler Taveira <euler(at)eulerto(dot)com>, Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: change default default_toast_compression to lz4? |
| Date: | 2026-03-04 07:15:50 |
| Message-ID: | CAGECzQQgMGQ_tvH+fN1QTpaUmrsmUatZCkT13PevVDQjtL3beg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 4 Mar 2026 at 06:05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Michael Paquier <michael(at)paquier(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2026-03-04 07:17:57 | Re: Need to install liblz4-dev |
| Previous Message | Hayato Kuroda (Fujitsu) | 2026-03-04 07:07:51 | RE: BUG: Former primary node might stuck when started as a standby |