-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Verify
-
None
-
Storage Engines, Storage Engines - Persistence
-
45.038
-
StorEng - Defined Pipeline
-
None
In WT-18582 we test the verify_internals config skips table verification by corrupting a table's file on disk. In this ticket we want to look at alternatives that prove the verify_internals config skips verifying each table without introducing a corruption. Possible ways are opening a cursor and see if it hits EBUSY, use WT stats to prove that the tables are not visited etc.
Also add edge case coverage for inputs around the new config: a named URI with verify_internals set (in this case verify_internals should do nothing), and the case where the input is not a correct URI nor NULL. The rejection behavior already exists today, we would want to add test coverage them and see if there's any gaps.
Nice-to-have cleanup, not urgent.
- is related to
-
WT-18582 Btree unique ID verification occurs for all stable URIs
-
- Closed
-