From 6e155d280dbe4bab171619654d8abc4b7f197e78 Mon Sep 17 00:00:00 2001 From: Mike Lissner Date: Thu, 30 Jul 2020 13:49:57 -0700 Subject: [PATCH] Added note about culling in database cache backend docs. Co-authored-by: Mariusz Felisiak --- docs/topics/cache.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 7bf9fcbbde..6ae1e1e376 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -195,6 +195,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 each time ``add()``, ``set()``, or ``touch()`` is called. + Creating the cache table ~~~~~~~~~~~~~~~~~~~~~~~~