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:35:01 -0400 |
| commit | 8e34bcdfba16cb1dc3096da57d1e82d3839472a8 (patch) | |
| tree | 860d29f02d8d0e643e24247a527c1d7eb529b395 | |
| parent | 3552afa25e0359d56191b1d692db59463222ad44 (diff) | |
[1.7.x] Fixed #23023 -- Added warning against local-memory cache.
Thanks django at kerz.id.au.
Backport of 7d0519c725 from master
| -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 8367d582ea..b8312fd0c4 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 |