Verify includes functionality to check that the metadata (and shared metadata) do not contain duplicate btree IDs. This check runs in O(n log n) due to sorting the list of btree IDs it found while scanning metadata.

Unfortunately, this check is performed for each URI the verify API is asked to check. As such, for a use case like MongoDB's where they choose one URI at a time to verify, we will perform the above O(n log n) verification for each table. (!!)

There isn't a "natural" fix for this – WiredTiger does verify every URI if you call verify without a URI, but for users that want to control which tables to verify, we should also offer a way to ask for "database-wide" validations.