release-25.4: sql: use INSPECT parameters to disambiguate index names #155722
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport 1/1 commits from #155475 on behalf of @bghal.
Previously, the indexes named in the
INSPECT
command's options wereresolved without using the database or table name as context. This
change uses the name of the table and/or database to fill out the index
name.
Some cleanup work from #148365 to move off of
SCRUB
is also included.Epic: CRDB-30356
Informs: #77376
Release note (sql change): The
INSPECT
command now uses the table ordatabase parameter as context for resolving indexes named in the
options.
Release justification: