Hi, On Sun, 8 Mar 2026 at 22:45, Manni Wood <[email protected]> wrote: > > As requested, here are some numbers based on the latest master but with the > copy code inlining excised (`git revert > dc592a41557b072178f1798700bf9c69cd8e4235`), compared to master with copy code > inlining left in place and the v11 patch applied. > Both results have lz4 compression in place.
Thank you for the benchmark! > I have not run numbers without lz4. I assume I could use the two postgres > instances that I have compiled with lz4, but just set > `default_toast_compression = pglz` in postgesql.conf for both instances. Let > me know if that is a mistaken assumption on my part. I am a bit confused. Are you asking that for the current benchmark you shared or future benchmarks? I assume your current benchmark has 'default_toast_compression = lz4' because your benchmark results are very similar to my benchmark with 'default_toast_compression = lz4' but I just wanted to make sure. What you said about editing postgresql.conf is correct but you need to make this change before creating the Postgres instance with 'pg_ctl ... start' command, otherwise it won't have an effect and you need to restart the instance to see the effect. Also, If you want to benchmark without lz4 change, you can just use the "SET default_toast_compression to 'pglz';" command in psql, then you don't need to edit postgresql.conf. Please note that this will affect only the psql instance you typed the command. To make things easier, you can run the 'SHOW default_toast_compression;' command to see the current value of 'default_toast_compression'. -- Regards, Nazir Bilal Yavuz Microsoft
