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
ui: update SQL API transaction contention query to not select from crdb_internal.ranges
#94445
Labels
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Comments
ericharmeling
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
T-sql-observability
labels
Dec 29, 2022
ericharmeling
changed the title
ui: update SQL API transaction contention query to
ui: update SQL API transaction contention query to not select from Jan 4, 2023
crdb_internal.ranges
crdb_internal.ranges
ericharmeling
added a commit
to ericharmeling/cockroach
that referenced
this issue
Jan 5, 2023
…db_internal.ranges Fixes cockroachdb#94445. This commit updates the SQL-over-HTTP query executed on behalf of the transaction insight details page to not select from the crdb_internal.ranges table, and instead select from other internal tables. Release note: None
ericharmeling
added a commit
to ericharmeling/cockroach
that referenced
this issue
Jan 6, 2023
…rdb_internal.ranges Fixes cockroachdb#94445. This commit updates the SQL-over-HTTP query executed on behalf of the transaction insight details page to not select from the crdb_internal.ranges table, and instead select from other internal tables. Release note: None
ericharmeling
added a commit
to ericharmeling/cockroach
that referenced
this issue
Jan 10, 2023
…rdb_internal.ranges Fixes cockroachdb#94445. This commit updates the SQL-over-HTTP query executed on behalf of the transaction insight details page to not select from the crdb_internal.ranges table, and instead select from other internal tables. Release note: None
ericharmeling
added a commit
to ericharmeling/cockroach
that referenced
this issue
Jan 11, 2023
…rdb_internal.ranges Fixes cockroachdb#94445. This commit updates the SQL-over-HTTP query executed on behalf of the transaction insight details page to not select from the crdb_internal.ranges table, and instead select from other internal tables. Release note: None
ericharmeling
added a commit
to ericharmeling/cockroach
that referenced
this issue
Jan 13, 2023
…rdb_internal.ranges Fixes cockroachdb#94445. This commit updates the SQL-over-HTTP query executed on behalf of the transaction insight details page to not select from the crdb_internal.ranges table, and instead select from other internal tables. Release note: None
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.
One of the SQL API queries for transaction contention insights joins on
crdb_internal.ranges
. We should update this query to not select fromcrdb_internal.ranges
and then backport this change to 22.2, for the following reasons:As of sql: better
SHOW RANGES
and changes tocrdb_internal.ranges{,_no_leases}
#93644, the problematic query selects columns that no longer exist incrdb_internal.ranges
(in specific,database_name
). As a result, the transaction insight details page on the console will hang/return an error for all cluster types (self-hosted, dedicated, serverless, etc).sql: support crdb_internal.ranges{_no_leases} for secondary tenants #92131 was not backported to 22.2. So querying
crdb_internal.ranges
from a 22.2 tenant cluster won't work. This is a blocker for https://github.com/cockroachlabs/managed-service/pull/10854.This issue only affects transaction insight details.
Jira issue: CRDB-22892
The text was updated successfully, but these errors were encountered: