3 ms·
That tone is asking for some passionate replies ;-) This isn't about PostgreSQL at all. There's things where relational databases are a good fit, and things th
by fredoliveira 16y ago
That tone is asking for some passionate replies ;-)
This isn't about PostgreSQL at all. There's things where relational databases are a good fit, and things that are a bad fit. As such, this isn't about what PostgreSQL does poorly, but about the cases where a key-value store with some pretty good data structures comes in handy. Would you really store temporary data in your relational database? Would you use it as a caching mechanism? Perhaps as a queue? Not unless you're crazy. So I guess this isn't about what PostgreSQL performs poorly, but about where Redis is a better solution.