diff options
| author | Tim Graham <timograham@gmail.com> | 2014-07-16 12:32:57 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-07-16 12:34:27 -0400 |
| commit | 7d0519c725f25cb0b52e42c60f2505e21d2ab4b3 (patch) | |
| tree | 6255d1c8e4de817592c3929fc28dedf3d4b4b424 /docs | |
| parent | 5954aa6db084b9e81960f095d2145c876fdbece4 (diff) | |
Fixed #23023 -- Added warning against local-memory cache.
Thanks django at kerz.id.au.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/http/sessions.txt | 4 |
1 files changed, 3 insertions, 1 deletions
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 |