Currently WiredTigerUtil::setTableLogging assumes that retrieving the table's metadata from WiredTiger will succeed, and in non-debug builds interprets garbage memory as a std::string if it fails. The metadata being missing can only happen due to a bug happening earlier, but we still do not want to perform an bad memory read when that happens.
Handle metadata errors in WiredTigerUtil::setTableLogging
- Assignee:
-
Thomas Goyne
- Reporter:
-
Thomas Goyne
- Votes:
-
0 Vote for this issue - Watchers:
-
5 Start watching this issue
- Created:
- Updated:
- Resolved: