timescale
Compression Troubleshooting: Inefficient compress_chunk_time_interval configuration
Please add the following part to the troubleshooting page for compression: https://docs.timescale.com/use-timescale/latest/compression/troubleshooting
Follow up of https://github.com/timescale/timescaledb/pull/7786
Title: Inefficient compress_chunk_time_interval configuration
Text:
When compress_chunk_time_interval is configured but compress_orderby does not have the primary dimension as the first column, chunk merging will be less efficient as chunks have to be decompressed to be merged. Please ensure the first column in compress_orderby is the primary dimension of the chunk.
TimescaleDB will show you the following hint:
compress_chunk_time_interval configured and primary dimension not first column in compress_orderby.
consider setting "<column name>" as first compress_orderby column
Thank you
@philkra thank you very much for thinking about adding this to docs :-) Can we add a quick explanation what to do when this hint is encountered? Even if it's completely obvious, the troubleshooting page should provide a solution.
