You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Earlier with v4, I experimented with default_toast_compression. There's a significant improvement in table size when using lz4 instead of pglz. It may be a good idea to advise to set default_toast_compression to lz4 before installing the PoWA repository, or maybe force lz4 in the extension, when available.
Do you want me to try to submit a patch to force lz4 compression ?
Kind regards
The text was updated successfully, but these errors were encountered:
sorry I forgot to answer. I agree that it's likely a good idea, but there are some caveat:
as you mentioned it's not available in all major versions, so simply forcing it when possible means that if you pg_upgrade from an older version you will never be able to use it
it's likely that eventually other compression methods will be available for TOAST so forcing it when possible could then become problematic
I think that we should provide a real SQL API to handle that (a function that changes the TOAST compression on all powa related tables) and store the information somewhere (so that we can distinguish explicit lz4 vs default lz4), and eventually a way to use those from the UI.
once we have all of that forcing the default at install time could be good.
Hello,
Earlier with v4, I experimented with default_toast_compression. There's a significant improvement in table size when using lz4 instead of pglz. It may be a good idea to advise to set default_toast_compression to lz4 before installing the PoWA repository, or maybe force lz4 in the extension, when available.
Do you want me to try to submit a patch to force lz4 compression ?
Kind regards
The text was updated successfully, but these errors were encountered: