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
[Bug]: Wrong check constraint on continuous_agg_migrate_plan_step.type for instances upgrading from 2.7.2 to 2.8.0 #4727
Comments
@fabriziomello I created a bug report for the issue discussed on Slack. /cc @horzsolt |
fabriziomello
added a commit
to fabriziomello/timescaledb
that referenced
this issue
Sep 21, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix timescale#4727
fabriziomello
added a commit
to fabriziomello/timescaledb
that referenced
this issue
Sep 21, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix timescale#4727
fabriziomello
added a commit
to fabriziomello/timescaledb
that referenced
this issue
Sep 22, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix timescale#4727
fabriziomello
added a commit
to fabriziomello/timescaledb
that referenced
this issue
Sep 22, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix timescale#4727
fabriziomello
added a commit
that referenced
this issue
Sep 22, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix #4727
jnidzwetzki
pushed a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Sep 29, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix timescale#4727
jnidzwetzki
pushed a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Sep 30, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix timescale#4727
jnidzwetzki
pushed a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Sep 30, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix timescale#4727
jnidzwetzki
pushed a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Sep 30, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix timescale#4727
jnidzwetzki
pushed a commit
to jnidzwetzki/timescaledb
that referenced
this issue
Oct 4, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix timescale#4727
jnidzwetzki
pushed a commit
that referenced
this issue
Oct 6, 2022
Instances upgraded to 2.8.0 will end up with a wrong check constraint in catalog table `continuous_aggregate_migrate_plan_step`. Fixed it by removing and adding the constraint with the correct checks. Fix #4727
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What type of bug is this?
Incorrect result
What subsystems and features are affected?
Continuous aggregate
What happened?
Instances upgrading from 2.7.2 to 2.8.0 are missing the
OVERRIDE CAGG
andDROP OLD CAGG
values for the CHECK CONSTRAINT oncontinuous_agg_migrate_plan_step.type
:This will happen in updated instances. New instances directly installed in 2.8 will not have this problem.
Quick reference:
Related slack discussion (internal only)
Reported by
@carobme
Additionally, we should check why this was not caught in our upgrade/downgrade tests (no error raised) in our CI and fix the tests.
TimescaleDB version affected
2.8.0 (upgrade from 2.7.2 only)
PostgreSQL version used
Not applicable
What operating system did you use?
Not applicable
What installation method did you use?
Not applicable
What platform did you run on?
Managed Service for TimescaleDB (MST/Aiven)
Relevant log output and stack trace
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: