-
Notifications
You must be signed in to change notification settings - Fork 848
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
Remove FK from continuous_agg_migrate_plan #5664
Merged
fabriziomello
merged 1 commit into
timescale:main
from
fabriziomello:remove_fk_from_cagg_migrate_plan
May 10, 2023
Merged
Remove FK from continuous_agg_migrate_plan #5664
fabriziomello
merged 1 commit into
timescale:main
from
fabriziomello:remove_fk_from_cagg_migrate_plan
May 10, 2023
Conversation
This file contains 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
@lkshminarayanan, @sb230132: please review this pull request.
|
Codecov Report
@@ Coverage Diff @@
## main #5664 +/- ##
==========================================
+ Coverage 90.97% 91.34% +0.36%
==========================================
Files 230 228 -2
Lines 54473 51920 -2553
==========================================
- Hits 49557 47424 -2133
+ Misses 4916 4496 -420 see 132 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
fabriziomello
force-pushed
the
remove_fk_from_cagg_migrate_plan
branch
2 times, most recently
from
May 5, 2023 18:14
daa5478
to
c6c586e
Compare
During the `cagg_migrate` execution if the user set the `drop_old` parameter to `true` the routine will drop the old Continuous Aggregate leading to an inconsistent state because the catalog code don't handle this table as a normal catalog table so the records are not removed when dropping a Continuous Aggregate. The same problem will happen if you manually drop the old Continuous Aggregate after the migration. Fixed it by removing the useless Foreign Key and also adding another column named `user_view_definition` to the main plan table just to store the original user view definition for troubleshooting purposes. Fixed timescale#5662
fabriziomello
force-pushed
the
remove_fk_from_cagg_migrate_plan
branch
from
May 8, 2023 12:19
c6c586e
to
623d257
Compare
lkshminarayanan
approved these changes
May 10, 2023
konskov
approved these changes
May 10, 2023
Automated backport to 2.10.x not done: cherry-pick failed. Git status
|
timescale-automation
added
the
auto-backport-not-done
Automated backport of this PR has failed non-retriably (e.g. conflicts)
label
May 10, 2023
fabriziomello
added
disable-auto-backport
Do not automatically backport this PR or fix of this issue
and removed
disable-auto-backport
Do not automatically backport this PR or fix of this issue
labels
May 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-backport-not-done
Automated backport of this PR has failed non-retriably (e.g. conflicts)
continuous_aggregate
disable-auto-backport
Do not automatically backport this PR or fix of this issue
Team: Core Database
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.
During the
cagg_migrate
execution if the user set thedrop_old
parameter totrue
the routine will drop the old Continuous Aggregate leading to an inconsistent state because the catalog code don't handle this table as a normal catalog table so the records are not removed when dropping a Continuous Aggregate. The same problem will happen if you manually drop the old Continuous Aggregate after the migration.Fixed it by removing the useless Foreign Key and also adding another column named
user_view_definition
to the main plan table just to store the original user view definition for troubleshooting purposes.Disable-check: force-changelog-changed
Fixed #5662