From 7d0519c725f25cb0b52e42c60f2505e21d2ab4b3 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 16 Jul 2014 12:32:57 -0400 Subject: [PATCH] Fixed #23023 -- Added warning against local-memory cache. Thanks django at kerz.id.au. --- docs/topics/http/sessions.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt index 936a3c5f5d..fca2abe872 100644 --- a/docs/topics/http/sessions.txt +++ b/docs/topics/http/sessions.txt @@ -64,7 +64,9 @@ sure you've configured your cache; see the :doc:`cache documentation cache backend. The local-memory cache backend doesn't retain data long enough to be a good choice, and it'll be faster to use file or database sessions directly instead of sending everything through the file or - database cache backends. + database cache backends. Additionally, the local-memory cache backend is + NOT multi-process safe, therefore probably not a good choice for production + environments. If you have multiple caches defined in :setting:`CACHES`, Django will use the default cache. To use another cache, set :setting:`SESSION_CACHE_ALIAS` to the