Skip to content

Conversation

svenklemm
Copy link
Member

@svenklemm svenklemm commented Jul 30, 2025

When a partially compressed chunk with segmentby column was
recompressed the new min/max range would not be calculated correctly
and only take the new values into account but not already compressed
values.

Disable-check: commit-count

Copy link

@philkra, @fabriziomello: please review this pull request.

Powered by pull-review

Copy link

codecov bot commented Jul 30, 2025

Codecov Report

❌ Patch coverage is 67.56757% with 12 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.28%. Comparing base (a10116b) to head (86a79d7).
⚠️ Report is 101 commits behind head on main.

Files with missing lines Patch % Lines
src/ts_catalog/chunk_column_stats.c 65.62% 3 Missing and 8 partials ⚠️
src/chunk_adaptive.c 66.66% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #8426      +/-   ##
==========================================
+ Coverage   82.21%   82.28%   +0.07%     
==========================================
  Files         247      247              
  Lines       46828    46831       +3     
  Branches    11855    11861       +6     
==========================================
+ Hits        38500    38537      +37     
- Misses       3516     3531      +15     
+ Partials     4812     4763      -49     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@svenklemm svenklemm added this to the v2.21.2 milestone Jul 30, 2025
@svenklemm svenklemm requested a review from antekresic July 31, 2025 07:33
@svenklemm svenklemm force-pushed the sven/chunk_skip branch 5 times, most recently from 8cc058c to 180a67d Compare July 31, 2025 10:16
When a partially compressed chunk with segmentby column was
recompressed the new min/max range would not be calculated correctly
and only take the new values into account but not already compressed
values.
@svenklemm svenklemm added the force-auto-backport Automatically backport this PR or fix of this issue, even if it's not marked as "bug" label Jul 31, 2025
@svenklemm svenklemm merged commit 4a4a384 into main Jul 31, 2025
47 of 49 checks passed
@svenklemm svenklemm deleted the sven/chunk_skip branch July 31, 2025 10:40
@philkra philkra mentioned this pull request Aug 5, 2025
philkra added a commit that referenced this pull request Aug 5, 2025
## 2.21.2 (2025-08-05)

This release contains performance improvements and bug fixes since the
2.21.1 release. We recommend that you upgrade at the next available
opportunity.

**Bugfixes**
* [#8418](#8418) Fix
duplicate constraints in JOIN queries
* [#8426](#8426) Fix chunk
skipping min/max calculation
* [#8434](#8434) Allow
`show_chunks` to process more than 65535 chunks
@timescale-automation timescale-automation added the released-2.21.2 Released in 2.21.2 label Aug 5, 2025
@svenklemm svenklemm mentioned this pull request Aug 26, 2025
@timescale-automation timescale-automation added the released-2.22.0 Released in 2.22.0 label Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backported-2.21.x force-auto-backport Automatically backport this PR or fix of this issue, even if it's not marked as "bug" released-2.21.2 Released in 2.21.2 released-2.22.0 Released in 2.22.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants