Collect relation-level stats during compression #7520
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During compression, column min/max stats are collected on a per-segment basis for orderby columns and those that have indexes.
This change uses the same mechanism to collect relation-level min/max stats to be used by chunk skipping. This avoids, in worst case, an extra full table scan to gather these chunk column stats.
For simplicity, stats gathering is enabled for all columns that can support it, even though a column might use neither segment-level stats nor relation-level (chunk column) stats. The overhead of collecting min/max values should be negligible.
Disable-check: force-changelog-file