[Enhancement]: Enable chunk skipping metadata for all columns by default

[pantonis]

What type of enhancement is this?

Performance

What subsystems and features will be improved?

Query executor

What does the enhancement do?

TimescaleDB should automatically save min/max metadata ranges for all columns (not just ORDER BY columns) during compression, similar to how Parquet handles column statistics. This would significantly improve analytical query performance with negligible storage overhead. Min/max metadata storage is minimal, but the performance benefits from batch/chunk skipping are substantial—this is a fundamental feature in modern columnar analytics engines.

Implementation challenges

No response

[JacobBrejnbjerg]

Agreed, however, when calculating min/max in the final steps of compressing a chunk it does an exclusive lock blocking all reads. With bigger chunks, this would be a problem like it is in our case. Making it default might cause problems for people unaware.