Allow concurrent policies on hierarchical CAggs#10048
Open
melihmutlu wants to merge 1 commit into
Open
Conversation
Multiple refresh policies on hierarchical continuous aggregates were blocked in timescale#8707 due to potential deadlocks observed with the initial concurrent refresh policy implementation. Since then the refresh concurrency machinery has been reworked and the blocker is no longer needed.
melihmutlu
force-pushed
the
hier_cagg_multiple_pol
branch
from
97ee6cc to
685f273
Compare
|
@svenklemm, @pnthao: please review this pull request.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
kpan2034
approved these changes
Jun 22, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Concurrent refresh policies on hierarchical continuous aggregates were blocked in #8707 due to potential deadlocks observed with the initial concurrent refresh policy implementation. Since then the refresh concurrency machinery has been reworked and the blocker is no longer needed.