Description
What type of enhancement is this?
Performance
What subsystems and features will be improved?
Continuous aggregate
What does the enhancement do?
When you refresh a continuous aggregate, it will as part of the processing move hypertable invalidations from the hypertable invalidation log to the materialization log before actually starting to perform the refresh based on the invalidations in the materialization invalidation log.
This means that if multiple refreshes execute at the same time, some of them will have to wait while the invalidations for a hypertable is processed, which can lead to unnecessary delays in updating the continuous aggregates.
This means that you might want to have a policy defined to process hypertable invalidations and you want the refresh policies to base their refresh on the latest materialization invalidations, even if they are slightly out of date.
This could be used to avoid blocking waiting for the processing to be done (if you have a lot of changes to the hypertable), but also to avoid jobs drifting because they are delayed.
Implementation challenges
No response