invalidation engine clarification for CAGGs #4557
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
Allow 10 minutes from last push for the staging site to build. If the link doesn't work, try using incognito mode instead. For internal reviewers, check web-documentation repo actions for staging build status. Link to build for this PR: http://docs-dev.timescale.com/docs-4552-feedback |
billy-the-fish
approved these changes
Nov 7, 2025
svenklemm
reviewed
Nov 10, 2025
Comment on lines
263
to
273
| When data older than the invalidation threshold is changed, each mutation | ||
| operation logs the minimum and maximum timestamps of the rows it modified. | ||
| The continuous aggregate then identifies which complete time buckets contain | ||
| these modified rows. Only those specific buckets are recalculated during refresh. | ||
|
|
||
| For example, if one operation modifies rows in the 10:00 bucket and another | ||
| modifies rows in the 15:00 bucket, only those two buckets are recalculated. The | ||
| buckets in between (11:00, 12:00, 13:00, 14:00) are not affected. | ||
|
|
||
| This logging does cause some write load. However, the threshold lags behind the | ||
| area of data that is currently changing, so the writes are small and rare. |
Member
There was a problem hiding this comment.
Hmm its more complicated than that, it depends how you define operation, the min/max tracking is per transaction so if you modify 10:00 and 15:00 in 1 transaction then all buckets in between would also be recalculated. If you modify 10:00 in a transaction and 15:00 in a separate transaction then intermediate values would not be recalculated
Contributor
Author
There was a problem hiding this comment.
Updated, thank you.
svenklemm
approved these changes
Nov 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.