-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
sql: create materalized view can cause panic #76710
Comments
Note: the underlying When directly creating the materialized view on the system table alone, the |
I think the observation which is legit is we should catch this panic and turn it into an error. Also, we shouldn't have this panic. |
This few lines look sus.
Looking at this line, it might be a null pointer error. cockroach/pkg/sql/crdb_internal.go Line 5114 in a204e69
My hypothesis here is that when an InternalExecutor executes an explicit transaction that reads from this virtual table, this panic can happen 🤔 |
…able Previously, a null pointer error in crdb_internal.cluster_statement_statistics can cause a runtime panic when it is read by internal executor. This commit fixes the null pointer error by properly propagating state in internalExtendedEvalCtx(). Partially resolves cockroachdb#76710 Release note (bug fix): creating materialized view on crdb_internal.cluster_statement_statistics no longer cause panic.
Describe the problem
Executing the following statement can cause a runtime panic:
To Reproduce
This can be reprodued from master.
Expected behavior
Do not panic.
Additional data / screenshots
Environment:
Epic: CRDB-13625
Jira issue: CRDB-13244
The text was updated successfully, but these errors were encountered: