With an existing hypertable, it is very easy to turn on compression and start compressing the data. Compression can be tailored using timescaledb.compress_segmentby and timescaledb.compress_orderby and will improve performance if used the right way.
Problem
Turning on compression for a hypertable can have unexpected effects in query performance and compression depending on what segmentby and orderby columns are selected.
Question
Can we create recommendations based on the schema and the statistics for the table that we want to enable compression for?
Background
With an existing hypertable, it is very easy to turn on compression and start compressing the data. Compression can be tailored using
timescaledb.compress_segmentbyandtimescaledb.compress_orderbyand will improve performance if used the right way.Problem
Turning on compression for a hypertable can have unexpected effects in query performance and compression depending on what segmentby and orderby columns are selected.
Question
Can we create recommendations based on the schema and the statistics for the table that we want to enable compression for?