-
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: v22.1.5: nil schema descriptor returned by GetImmutableSchemaByID #87895
Labels
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-sentry
Originated from an in-the-wild panic report.
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Comments
cockroach-teamcity
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-sentry
Originated from an in-the-wild panic report.
labels
Sep 13, 2022
yuzefovich
changed the title
sentry: conn_executor.go:754: runtime error: invalid memory address or nil pointer dereference
(1) attached stack trace
-- stack trace:
| github.com/cockroachdb/cockroach/pkg/sql.(*Server).ServeConn.func1...
sql: v22.1.5: nil schema descriptor returned by GetImmutableSchemaByID
Sep 21, 2022
ajwerner
added a commit
to ajwerner/cockroach
that referenced
this issue
Sep 23, 2022
A schema might not exist because it has been dropped. We need to mark the lookup as required. Fixes cockroachdb#87895 Release note (bug fix): Fixed a bug in pg_catalog tables which could result in an internal error if a schema is concurrently dropped.
craig bot
pushed a commit
that referenced
this issue
Sep 23, 2022
87533: sqlliveness: add timeouts to heartbeats r=ajwerner a=aadityasondhi Previously, sqlliveness heartbeat operations could block on the transactions that were involved. This change introduces some timeouts of the length of the heartbeat during the create and refresh operations. Resolves #85541 Release note: None Release justification: low-risk bugfix to existing functionality 88293: backupccl: elide expensive ShowCreate call in SHOW BACKUP r=stevendanna a=adityamaru In #88376 we see the call to `ShowCreate` taking ~all the time on a cluster with 2.5K empty tables. In all cases except `SHOW BACKUP SCHEMAS` we do not need to construct the SQL representation of the table's schema. This results in a marked improvement in the performance of `SHOW BACKUP` as can be seen in #88376 (comment). Fixes: #88376 Release note (performance improvement): `SHOW BACKUP` on a backup containing several table descriptors is now more performant 88471: sql/schemachanger: plumb context, check for cancelation sometimes r=ajwerner a=ajwerner Fixes #87246 This will also improve tracing. Release note: None 88557: testserver: add ShareMostTestingKnobsWithTenant option r=msbutler a=stevendanna The new ShareMostTestingKnobs copies nearly all of the testing knobs specified for a TestServer to any tenant started for that server. The goal here is to make it easier to write tests that depend on testing hooks that work under probabilistic tenant testing. Release justification: non-production code change Release note: None 88562: upgrade grpc to v.1.49.0 r=erikgrinaker a=pavelkalinnikov Fixes #81881 Touches #72083 Release note: upgraded grpc to v1.49.0 to fix a few panics that the old version caused 88568: sql: fix panic due to missing schema r=ajwerner a=ajwerner A schema might not exist because it has been dropped. We need to mark the lookup as required. Fixes #87895 Release note (bug fix): Fixed a bug in pg_catalog tables which could result in an internal error if a schema is concurrently dropped. Co-authored-by: David Hartunian <[email protected]> Co-authored-by: Aaditya Sondhi <[email protected]> Co-authored-by: adityamaru <[email protected]> Co-authored-by: Andrew Werner <[email protected]> Co-authored-by: Steven Danna <[email protected]> Co-authored-by: Pavel Kalinnikov <[email protected]>
blathers-crl bot
pushed a commit
that referenced
this issue
Sep 23, 2022
A schema might not exist because it has been dropped. We need to mark the lookup as required. Fixes #87895 Release note (bug fix): Fixed a bug in pg_catalog tables which could result in an internal error if a schema is concurrently dropped.
blathers-crl bot
pushed a commit
that referenced
this issue
Sep 23, 2022
A schema might not exist because it has been dropped. We need to mark the lookup as required. Fixes #87895 Release note (bug fix): Fixed a bug in pg_catalog tables which could result in an internal error if a schema is concurrently dropped.
exalate-issue-sync
bot
added
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
and removed
T-sql-schema-deprecated
Use T-sql-foundations instead
labels
May 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-sentry
Originated from an in-the-wild panic report.
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
This issue was autofiled by Sentry. It represents a crash or reported error on a live cluster with telemetry enabled.
Sentry link: https://sentry.io/organizations/cockroach-labs/issues/3585175124/?referrer=webhooks_plugin
Panic message:
Stacktrace (expand for inline code snippets):
cockroach/pkg/sql/conn_executor.go
Lines 753 to 755 in a30a663
GOROOT/src/runtime/panic.go#L1037-L1039 in runtime.gopanic
cockroach/pkg/sql/colexecerror/error.go
Lines 57 to 59 in a30a663
GOROOT/src/runtime/panic.go#L1037-L1039 in runtime.gopanic
cockroach/pkg/sql/colexecerror/error.go
Lines 57 to 59 in a30a663
GOROOT/src/runtime/panic.go#L1037-L1039 in runtime.gopanic
cockroach/pkg/sql/colexecerror/error.go
Lines 57 to 59 in a30a663
GOROOT/src/runtime/panic.go#L1037-L1039 in runtime.gopanic
cockroach/pkg/sql/colexecerror/error.go
Lines 57 to 59 in a30a663
GOROOT/src/runtime/panic.go#L1037-L1039 in runtime.gopanic
cockroach/pkg/sql/colexecerror/error.go
Lines 57 to 59 in a30a663
GOROOT/src/runtime/panic.go#L1037-L1039 in runtime.gopanic
cockroach/pkg/sql/colexecerror/error.go
Lines 57 to 59 in a30a663
GOROOT/src/runtime/panic.go#L1037-L1039 in runtime.gopanic
cockroach/pkg/sql/colexecerror/error.go
Lines 57 to 59 in a30a663
GOROOT/src/runtime/panic.go#L1037-L1039 in runtime.gopanic
cockroach/pkg/sql/colexecerror/error.go
Lines 57 to 59 in a30a663
GOROOT/src/runtime/panic.go#L1037-L1039 in runtime.gopanic
GOROOT/src/runtime/panic.go#L220-L222 in runtime.panicmem
GOROOT/src/runtime/signal_windows.go#L253-L255 in runtime.sigpanic
cockroach/pkg/sql/pg_catalog.go
Lines 1124 to 1126 in a30a663
cockroach/pkg/sql/virtual_schema.go
Lines 664 to 666 in a30a663
cockroach/pkg/sql/virtual_table.go
Lines 319 to 321 in a30a663
cockroach/pkg/sql/plan_node_to_row_source.go
Lines 190 to 192 in a30a663
cockroach/pkg/sql/colexec/columnarizer.go
Lines 228 to 230 in a30a663
cockroach/pkg/sql/colflow/stats.go
Lines 98 to 100 in a30a663
cockroach/pkg/sql/colexecerror/error.go
Lines 90 to 92 in a30a663
cockroach/pkg/sql/colflow/stats.go
Lines 106 to 108 in a30a663
cockroach/pkg/sql/colexec/colexechash/hashtable.go
Lines 443 to 445 in a30a663
cockroach/pkg/sql/colexec/colexecjoin/hashjoiner.go
Lines 317 to 319 in a30a663
cockroach/pkg/sql/colexec/colexecjoin/hashjoiner.go
Lines 279 to 281 in a30a663
cockroach/pkg/sql/colexec/disk_spiller.go
Lines 197 to 199 in a30a663
v22.1.5
Jira issue: CRDB-19581
The text was updated successfully, but these errors were encountered: