You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
152352: sql: include isolation level in SHOW TRANSACTIONS, SHOW QUERIES, SHOW SESSIONS r=rytaft a=rytaft
This change adds isolation level information to the output of `SHOW
TRANSACTIONS`, `SHOW QUERIES`, and `SHOW SESSIONS` commands. The isolation level
is obtained from the session's active transaction information that is already
collected by the underlying gRPC endpoints.
Changes:
- Added `isolation_level` column to `SHOW TRANSACTIONS` output
- Updated `crdb_internal.node_queries` and `cluster_queries` table schemas to
include `isolation_level` column
- Updated `populateQueriesTable` to populate isolation level from session's
active transaction, or fall back to session's default isolation level
- Added `isolation_level` column to `SHOW QUERIES` output
- Updated `crdb_internal.node_sessions` and `cluster_sessions` table schemas to
include `isolation_level` column
- Updated `populateSessionsTable` to populate isolation level from session's
active transaction, or fall back to session's default isolation level
- Added `isolation_level` column to `SHOW SESSIONS` output
- Added `default_isolation_level` field to `Session` protobuf message
- Modified session serialization to include the session's default isolation
level
The isolation level now displays the session's default isolation level when
there is no active transaction, instead of NULL. This provides more useful
information to users about the transaction isolation level that would be used
for new transactions.
Fixes#150779
Release note (sql change): SQL observability commands `SHOW TRANSACTIONS`,
`SHOW QUERIES`, and `SHOW SESSIONS` now include an `isolation_level` column showing
the isolation level of the active transaction, or the session's default
isolation level when there is no active transaction.
152585: CODEOWNERS: add /pkg/server/storage_api to obs-prs r=dhartunian a=dhartunian
Epic: None
Release note: None
152675: allocator: correct logging for priority assertion r=tbg a=wenyihu6
This commit fixes an incorrect log statement in computeAction for priority
assertions. The log was mistakenly emitted even when the priority was not -1.
Related: #152512
Epic: none
Release note: none
Co-authored-by: Rebecca Taft <[email protected]>
Co-authored-by: David Hartunian <[email protected]>
Co-authored-by: wenyihu6 <[email protected]>
Copy file name to clipboardExpand all lines: docs/generated/http/full.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2315,6 +2315,7 @@ Session represents one SQL session.
2315
2315
| trace_id |[uint64](#cockroach.server.serverpb.ListSessionsResponse-uint64)|| The ID of the session's active trace. It will be 0 if tracing is off. |[reserved](#support-status)|
2316
2316
| goroutine_id |[int64](#cockroach.server.serverpb.ListSessionsResponse-int64)|| The ID of the session's goroutine. |[reserved](#support-status)|
| default_isolation_level |[string](#cockroach.server.serverpb.ListSessionsResponse-string)|| The session's default transaction isolation level. |[reserved](#support-status)|
2318
2319
2319
2320
2320
2321
@@ -2465,6 +2466,7 @@ Session represents one SQL session.
2465
2466
| trace_id |[uint64](#cockroach.server.serverpb.ListSessionsResponse-uint64)|| The ID of the session's active trace. It will be 0 if tracing is off. |[reserved](#support-status)|
2466
2467
| goroutine_id |[int64](#cockroach.server.serverpb.ListSessionsResponse-int64)|| The ID of the session's goroutine. |[reserved](#support-status)|
0 commit comments