| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | 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 05:05:14 |
| Message-ID: | 1341768.1772600714@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
I think it might be a good idea to add a field to pg_control
showing whether the cluster has ever been run with lz4 toast
compression, so that a non-lz4-enabled build could refuse
to start rather than encountering unexpected errors later.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2026-03-04 05:07:22 | Re: Improve checks for GUC recovery_target_xid |
| Previous Message | Chao Li | 2026-03-04 04:52:02 | Re: change default default_toast_compression to lz4? |