From 1d714484f67777e586fbea49ec743a7e39cba50f Mon Sep 17 00:00:00 2001 From: VIZZARD-X Date: Thu, 11 Jun 2026 20:47:20 +0530 Subject: Fixed #37129 -- Clarified database cache culling behavior in docs. --- docs/topics/cache.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 587a91859e..cc2459598c 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -253,8 +253,10 @@ In this example, the cache table's name is ``my_cache_table``:: } Unlike other cache backends, the database cache does not support automatic -culling of expired entries at the database level. Instead, expired cache -entries are culled when an ``add()``, ``set()``, or ``touch()`` is called. +culling of expired entries at the database level. Instead, an expired cache +entry is deleted when evaluated by a ``get()`` request. Furthermore, +expired cache entries are culled when ``add()``, ``set()``, or ``touch()`` +is called and the number of entries exceeds ``MAX_ENTRIES``. Since the cull operation can be expensive for a large cache, you may control how often this check occurs by setting ``CULL_PROBABILITY`` to a value between -- cgit v1.3