-
Type:
Technical Debt
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Block Cache
-
None
-
Storage Engines, Storage Engines - Persistence
-
SE Persistence backlog
-
None
Currently before calling __wti_blkcache_remove, we always perform a check for whether the given block had been configured, so we then move forward with the remove process. For example:
/* Evict the freed block from the block cache */ if (blkcache->type != WT_BLKCACHE_UNCONFIGURED) __wti_blkcache_remove(session, addr, addr_size);
Since this is a necessary check before calling __wti_blkcache_remove, it'd be nice if we can move this check inside __wti_blkcache_remove, following similar logic to that in __wt_blkcache_destroy.