-
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
Assertion IS_VALID_CHUNK(chunk) fails in CI run #4900
Labels
Comments
mkindahl
added a commit
to mkindahl/timescaledb
that referenced
this issue
Dec 9, 2022
A cache is used for the duration of a query to speed up planning time, but when destroying the cache, an error in the destruction would leave the cache pointer pointing to a partially or fully destroyed cache, which would give incorrect cache hits for the next query. This commit changes the order of the assignment so that the cache pointer is cleared before destroying the cache. This will allocate a new cache for the next query, even if the previous destruction had an error. Fixes timescale#4900
mkindahl
added a commit
to mkindahl/timescaledb
that referenced
this issue
Dec 9, 2022
A cache is used for the duration of a query to speed up planning time, but when destroying the cache, an error in the destruction would leave the cache pointer pointing to a partially or fully destroyed cache, which would give incorrect cache hits for the next query. This commit changes the order of the assignment so that the cache pointer is cleared before destroying the cache. This will allocate a new cache for the next query, even if the previous destruction had an error. Fixes timescale#4900
@jnidzwetzki is #5074 a fix for this? |
Seems #5086 fixes it. Closing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For some reason chunk->relkind is 0
Link to failed run:
https://github.com/timescale/timescaledb/actions/runs/3352772875/jobs/5555143368
Stacktrace:
The text was updated successfully, but these errors were encountered: