Fix cagg_migrate_to_time_bucket during update #7763
+19
−20
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.
In #6837 we added a migration for CAggs using
time_bucket_ng
to use the new version oftime_bucket
that support orign and/or offset.We made a mistake because we place the code to migrate existing CAggs using
time_bucket_ng
totime_bucket
in the update script but this code should be placed instead on post-update.sql script where we can call functions from the new extension version loaded.Disable-check: force-changelog-file