Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix refresh on empty CAgg with variable bucket #6660

Merged
merged 1 commit into from
Feb 16, 2024

Conversation

jnidzwetzki
Copy link
Contributor

So far, we have not handled CAggs with variable buckets correctly. The CAgg refresh on a hypertable without any data lead to the error message "timestamp out of range". This patch fixes the problem by declaring empty CAggs as up-to-date.

Copy link

codecov bot commented Feb 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (59f50f2) 80.06% compared to head (29e1dd1) 81.57%.
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6660      +/-   ##
==========================================
+ Coverage   80.06%   81.57%   +1.51%     
==========================================
  Files         190      190              
  Lines       37181    36307     -874     
  Branches     9450     9435      -15     
==========================================
- Hits        29770    29619     -151     
+ Misses       2997     2940      -57     
+ Partials     4414     3748     -666     

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

@jnidzwetzki jnidzwetzki marked this pull request as ready for review February 15, 2024 14:13
Copy link

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

Powered by pull-review

@jnidzwetzki jnidzwetzki force-pushed the cagg_range_undefined branch 3 times, most recently from be0d8d0 to c6313b6 Compare February 15, 2024 14:29
So far, we have not handled CAggs with variable buckets correctly. The
CAgg refresh on a hypertable without any data lead to the error message
"timestamp out of range". This patch fixes the problem by declaring
empty CAggs as up-to-date.
@jnidzwetzki jnidzwetzki merged commit 1f217ed into timescale:main Feb 16, 2024
44 checks passed
@jnidzwetzki jnidzwetzki deleted the cagg_range_undefined branch February 16, 2024 17:28
@svenklemm svenklemm added this to the TimescaleDB 2.14.2 milestone Feb 19, 2024
svenklemm added a commit to svenklemm/timescaledb that referenced this pull request Feb 19, 2024
This release contains bug fixes since the 2.14.1 release.
We recommend that you upgrade at the next available opportunity.

**Bugfixes**
* timescale#6655 Fix segfault in cagg_validate_query
* timescale#6660 Fix refresh on empty CAgg with variable bucket
* timescale#6670 Don't try to compress osm chunks

**Thanks**
* @kav23alex for reporting a segfault in cagg_validate_query
svenklemm added a commit that referenced this pull request Feb 20, 2024
This release contains bug fixes since the 2.14.1 release.
We recommend that you upgrade at the next available opportunity.

**Bugfixes**
* #6655 Fix segfault in cagg_validate_query
* #6660 Fix refresh on empty CAgg with variable bucket
* #6670 Don't try to compress osm chunks

**Thanks**
* @kav23alex for reporting a segfault in cagg_validate_query
svenklemm added a commit that referenced this pull request Feb 20, 2024
This release contains bug fixes since the 2.14.1 release.
We recommend that you upgrade at the next available opportunity.

**Bugfixes**
* #6655 Fix segfault in cagg_validate_query
* #6660 Fix refresh on empty CAgg with variable bucket
* #6670 Don't try to compress osm chunks

**Thanks**
* @kav23alex for reporting a segfault in cagg_validate_query
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants