So presumably the reason why you'd do something like this is if you have expensive queries or calculations, but in that case you could use materialized views in

So presumably the reason why you'd do something like this is if you have expensive queries or calculations, but in that case you could use materialized views instead, depending on your data and queries obviously. If it's to serve as a cache on an application level, memcache seems like it would be simpler and faster. While I do like Redis, I can see why you'd be careful introducing it. Redis can blur the boundaries between caching and data storage a bit, but it's just so handy.