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
Previously, the INSPECT command was a no-op that performed no actual
checking. This change implements the first consistency check for
INSPECT: index consistency checking, currently supporting a single
index at a time.
The consistency checking uses a full outer join between the primary
index and secondary index access paths to identify rows that exist
in one index but not the other, detecting potential corruption or
inconsistency issues.
This new functionality is integrated into the INSPECT job and
triggered through SCRUB when the enable_scrub_job setting is enabled.
Future work will expose this through direct INSPECT SQL commands.
Note for reviewers:
- Some tests currently generate internal errors in the SQL query
engine. These are not logged as INSPECT issues for now and will be
resolved in subsequent work.
- I include a crdb_internal.void_func() predicate in the query to
prevent the optimizer from optimizing the join away. There were
a couple of other options (add barrier option to CTE, materialize
the CTE inline), but this was the preferred method.
Release note: None
Epic: CRDB-30356
0 commit comments