-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Sentry: alter_table.go:1262: identity column × of relation × has 0 sequences instead of 1 (1) Wraps: (2) assertion failure Wraps: (3) attached stack trace -- stack trace: | github.com/cockroachd... #138925
Comments
CC'ing via the CODEOWNERS-based sentry heuristic:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
I'll try to search in Datadog to see if I can identify which cluster this came from. |
friendly_id: crl-prod-j77 |
This column looks strange. Since it has
That helped me come up with a simple repro. The following is allowed in 24.2 and earlier, but it shouldn't be:
In 24.3 we block this, and it fails with:
|
139084: sql: relax validation for IDENTITY columns r=rafiss a=rafiss The validations added in 4f99f9c were too strict. This patch makes it so we can continue having IDENTITY columns that are not backed by a sequence. This can happen if a SERIAL column is created with IDENTITY, and serial_normalization=rowid. informs #138925 informs #138972 Release note (bug fix): Fixed a bug where columns created with GENERATED ... BY IDENTITY with the SERIAL type could incorrectly fail internal validations. Co-authored-by: Rafi Shamim <[email protected]>
After more discussion, we've decided to continue with the 24.2 behavior of allowing this kind of column. Removing the IDENTITY property would be too destructive a change, since one property of those columns is that they cannot be written to. Instead, we will make the validations less strict, so that an IDENTITY column can be backed by |
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/6216371960/?referrer=webhooks_plugin
Panic Message:
Stacktrace (expand for inline code snippets):
pkg/sql/conn_executor_exec.go#L139-L141
pkg/sql/conn_executor_exec.go#L3450-L3452
pkg/sql/conn_executor_exec.go#L140-L142
pkg/sql/conn_executor_exec.go#L1186-L1188
pkg/sql/conn_executor_exec.go#L1980-L1982
pkg/sql/conn_executor_exec.go#L2434-L2436
pkg/sql/distsql_running.go#L1733-L1735
pkg/sql/distsql_running.go#L1730-L1732
pkg/sql/distsql_running.go#L2016-L2018
pkg/sql/distsql_running.go#L923-L925
pkg/sql/colflow/vectorized_flow.go#L299-L301
pkg/sql/flowinfra/flow.go#L573-L575
pkg/sql/execinfra/processorsbase.go#L725-L727
pkg/sql/colflow/flow_coordinator.go#L109-L111
pkg/sql/colexecerror/error.go#L161-L163
pkg/sql/colflow/flow_coordinator.go#L110-L112
pkg/sql/colexec/materializer.go#L226-L228
pkg/sql/colexecerror/error.go#L161-L163
pkg/sql/colexec/materializer.go#L227-L229
pkg/sql/colflow/stats.go#L97-L99
pkg/sql/colexecerror/error.go#L161-L163
pkg/sql/colflow/stats.go#L88-L90
pkg/sql/colexec/columnarizer.go#L177-L179
pkg/sql/plan_node_to_row_source.go#L165-L167
pkg/sql/plan.go#L527-L529
pkg/sql/walk.go#L37-L39
pkg/sql/walk.go#L73-L75
pkg/sql/walk.go#L293-L295
pkg/sql/walk.go#L106-L108
pkg/sql/plan.go#L524-L526
pkg/sql/alter_table.go#L640-L642
pkg/sql/alter_table.go#L1261-L1263
Tags
Jira issue: CRDB-46428
The text was updated successfully, but these errors were encountered: