A django cache backend that treats the db cache as a first class citizen.
The cache backend in django.core.cache.backends.db only works on the default database connection. Using the same connection as for regular model access can cause weird transaction related deadlocks and similar problems.
django-dbcache allows using a separate database connection just for cache.
Eventually this backend should implement database specific optimisations, like using postgres' key value store.
Why? Redis is probably faster than postgres, but it also has everything in RAM. For caches that don't get used that often, or have values that can stay in the cache unchanged for a very long time, postgres actually has better characteristics than redis. It does all sorts of optimisations on read or frequent access. For large installations with many, many not so active websites the resource usage characteristics of postgres are better than redis, which has a high idle consumption.