Recompression Needed For Chunk Skipping

TimescaleDB and PostgreSQL
1

According to the documentation enable_chunk_skipping, " Enable range statistics for a specific column in a compressed hypertable. This tracks a range of values for that column per chunk. Used for chunk pruning during query optimization."

If I enable chunk skipping do I need to re-compress any existing chunks in my database or run ANALYZE or anything like that to get the statistics created on the compressed chunks of the hyper table?

2

Welcome @chris-morris-h2o , you’ll need to decompress and recompress them.

For now, we don’t have any utility function to cover it. If you think it would be important for the community workflow/experience, feel free to suggest it as a feature in the github of the timescaledb extension.

1 Like