-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Cache and Eviction
-
None
-
Storage Engines - Transactions
-
962.036
-
SE Transactions - 2026-07-03
-
5
Sometimes we write data that we expect not to need to read back again any time soon, so it might be helpful to have a hint we can pass to set the retention priority for that data in the cache to be low, similar to "read once" hints used for scans.
This idea came up in the context of brainstorming how to mitigate cache effects from the additional writes performed by index builds.