-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
opt: v23.1.14: partial index predicate does not exist in table metadata #118913
Comments
Hi, @yuzefovich |
@XiaochenCui thanks for your interest! I don't think anyone is actively looking into this, so please feel free to take a stab. Note, though, the automatically-filed sentry issues don't have a reproduction, so debugging this type of issue usually involves some trial and error in hopes of getting a repro while reading the relevant code to get ideas on what could have gone wrong. (And we often don't find anything, so the issue is closed as unactionable. Still, we try to add some more debugging information if possible to the code, like a better error message.) |
The lack of reproduction doesn't matter, it's normal in db domain. The only issue is I'm new to crdb and may give my feedback for this issue in a long time (like 2 months). Do you think it's ok? And I don't have the permission for sentry.io |
Yeah, totally, there is definitely no rush in looking into this (as you can see, this issue has stayed in the "triage" column for over 2 months at this point). Re: access to sentry.io: I don't think that we'll be able to share access to sentry.io with you, but also the sentry event doesn't really contain any more debugging information other than what's included on this github issue (i.e. we only have a stack trace and the corresponding CRDB version). (I looked at the event for #124240 since the sentry event for #118913 seems to have been deleted.) |
@yuzefovich Thanks for your information |
This issue was auto filed by Sentry. It represents a crash or reported error on a live cluster with telemetry enabled.
Sentry Link: https://cockroach-labs.sentry.io/issues/4954614362/?referrer=webhooks_plugin
Panic Message:
Stacktrace (expand for inline code snippets):
src/runtime/asm_arm64.s#L1171-L1173
cockroach/pkg/sql/pgwire/conn.go
Lines 309 to 311 in b95f222
cockroach/pkg/sql/conn_executor.go
Lines 901 to 903 in b95f222
cockroach/pkg/sql/conn_executor.go
Lines 2104 to 2106 in b95f222
cockroach/pkg/sql/conn_executor.go
Lines 2187 to 2189 in b95f222
cockroach/pkg/sql/conn_executor.go
Lines 2182 to 2184 in b95f222
cockroach/pkg/sql/conn_executor_exec.go
Lines 140 to 142 in b95f222
cockroach/pkg/sql/conn_executor_exec.go
Lines 3118 to 3120 in b95f222
cockroach/pkg/sql/conn_executor_exec.go
Lines 141 to 143 in b95f222
cockroach/pkg/sql/conn_executor_exec.go
Lines 1036 to 1038 in b95f222
cockroach/pkg/sql/conn_executor_exec.go
Lines 1566 to 1568 in b95f222
cockroach/pkg/sql/conn_executor_exec.go
Lines 2059 to 2061 in b95f222
cockroach/pkg/sql/plan_opt.go
Lines 244 to 246 in b95f222
cockroach/pkg/sql/plan_opt.go
Lines 597 to 599 in b95f222
cockroach/pkg/sql/opt/xform/optimizer.go
Lines 268 to 270 in b95f222
cockroach/pkg/sql/opt/xform/optimizer.go
Lines 522 to 524 in b95f222
cockroach/pkg/sql/opt/xform/optimizer.go
Lines 577 to 579 in b95f222
cockroach/pkg/sql/opt/xform/optimizer.go
Lines 298 to 300 in b95f222
cockroach/pkg/sql/opt/xform/optimizer.go
Lines 535 to 537 in b95f222
cockroach/pkg/sql/opt/xform/explorer.go
Lines 184 to 186 in b95f222
https://github.com/cockroachdb/cockroach/blob/b95f2225b09cf25f9f2be31ef6a6f65c73a1b081/bazel-out/k8-opt/bin/pkg/sql/opt/xform/explorer.og.go#L21-L23
https://github.com/cockroachdb/cockroach/blob/b95f2225b09cf25f9f2be31ef6a6f65c73a1b081/bazel-out/k8-opt/bin/pkg/sql/opt/xform/explorer.og.go#L158-L160
cockroach/pkg/sql/opt/xform/scan_funcs.go
Lines 50 to 52 in b95f222
cockroach/pkg/sql/opt/xform/scan_index_iter.go
Lines 207 to 209 in b95f222
cockroach/pkg/sql/opt/xform/scan_index_iter.go
Lines 245 to 247 in b95f222
cockroach/pkg/sql/opt/table_meta.go
Lines 442 to 444 in b95f222
Tags
Jira issue: CRDB-35957
The text was updated successfully, but these errors were encountered: