-
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: v21.2.5: SET TRANSACTION AS OF SYSTEM TIME should have a nice error if reads were already performed #77265
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
Mar 2, 2022
blathers-crl
bot
added
the
T-sql-foundations
SQL Foundations Team (formerly SQL Schema + SQL Sessions)
label
Mar 4, 2022
jordanlewis
changed the title
sentry: txn_coord_sender.go:1047: cannot set fixed timestamp, txn "sql txn" meta={id=8ee478ca pri=0.00459305 epo=0 ts=1646203224.865911984,0 min=1646203224.865911984,0 seq=0} lock=false stat=PENDING rts=1646203224.865911984,0 wto=false gul=1646203224.865911984,0 already performed reads
--
*errutil.leafError: cannot set fixed timestamp, txn "sql txn" meta={id=8ee478ca pri=0.00459305 epo=0 ts=1646203224.865911984,0 min=1646203224.865911984,0 seq=0} lock=false stat=PENDING rts=1646203224.865911984,0 wto=false gul=1646203224.865911984,0 already performed reads (1)
txn_coord_sender.go:1047: *withstack.withStack (top exception)
*assert.withAssertionFailure
*contexttags.withContext: n1 (2)
(check the extra data payloads)
sentry: setHistoricalTimestamp from optBuilder after txn has already performed reads?
Mar 4, 2022
Tagging @cockroachdb/sql-experience because I'm thinking that it's unexpected that a txn has been able to perform reads before setting a historical timestamp. |
rafiss
changed the title
sentry: setHistoricalTimestamp from optBuilder after txn has already performed reads?
sql: v21.2.5: setHistoricalTimestamp from optBuilder after txn has already performed reads?
Mar 7, 2022
I think this is a case of an unhandled error case that definitely should be handled. Here's a repro:
|
rafiss
changed the title
sql: v21.2.5: setHistoricalTimestamp from optBuilder after txn has already performed reads?
sql: v21.2.5: SET TRANSACTION AS OF SYSTEM TIME should have a nice error if reads were already performed
Mar 7, 2022
This was referenced Jun 24, 2022
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/3059755899/?referrer=webhooks_plugin
Panic message:
Stacktrace (expand for inline code snippets):
cockroach/pkg/kv/kvclient/kvcoord/txn_coord_sender.go
Lines 1046 to 1048 in 5afb632
cockroach/pkg/kv/txn.go
Lines 1390 to 1392 in 5afb632
cockroach/pkg/sql/txn_state.go
Lines 271 to 273 in 5afb632
cockroach/pkg/sql/conn_executor.go
Lines 2332 to 2334 in 5afb632
cockroach/pkg/sql/set_transaction.go
Lines 36 to 38 in 5afb632
cockroach/pkg/sql/opaque.go
Lines 191 to 193 in 5afb632
cockroach/pkg/sql/opaque.go
Lines 60 to 62 in 5afb632
cockroach/pkg/sql/opt/optbuilder/opaque.go
Lines 68 to 70 in 5afb632
cockroach/pkg/sql/opt/optbuilder/builder.go
Lines 373 to 375 in 5afb632
cockroach/pkg/sql/opt/optbuilder/builder.go
Lines 240 to 242 in 5afb632
cockroach/pkg/sql/opt/optbuilder/builder.go
Lines 214 to 216 in 5afb632
cockroach/pkg/sql/plan_opt.go
Lines 520 to 522 in 5afb632
cockroach/pkg/sql/plan_opt.go
Lines 193 to 195 in 5afb632
cockroach/pkg/sql/conn_executor_exec.go
Lines 1259 to 1261 in 5afb632
cockroach/pkg/sql/conn_executor_exec.go
Lines 971 to 973 in 5afb632
cockroach/pkg/sql/conn_executor_exec.go
Lines 708 to 710 in 5afb632
cockroach/pkg/sql/conn_executor_exec.go
Lines 128 to 130 in 5afb632
cockroach/pkg/sql/conn_executor_exec.go
Lines 215 to 217 in 5afb632
cockroach/pkg/sql/conn_executor.go
Lines 1772 to 1774 in 5afb632
cockroach/pkg/sql/conn_executor.go
Lines 1774 to 1776 in 5afb632
cockroach/pkg/sql/conn_executor.go
Lines 1628 to 1630 in 5afb632
cockroach/pkg/sql/conn_executor.go
Lines 667 to 669 in 5afb632
cockroach/pkg/sql/pgwire/conn.go
Lines 647 to 649 in 5afb632
/usr/local/go/src/runtime/asm_amd64.s#L1370-L1372 in runtime.goexit
v21.2.5
Jira issue: CRDB-13565
The text was updated successfully, but these errors were encountered: