4 ms·

You can use Postgres for caching, and many other things. https://www.amazingcto.com/postgres-for-everything/ https://www.amazingcto.com/postgres-for-everything

You can use Postgres for caching, and many other things. https://www.amazingcto.com/postgres-for-everything/ https://www.amazingcto.com/postgres-for-everything/

ilyt 3y ago
Missing the point entirely
- jmartrican 3y ago
  I was responding to this comment. > I don't think it's even possible to use postgres as a traditional cache. The link I posted shows that you can use Postgres as a traditional cache. Specifically, the SO link showing that Postgres cannot do caching (expiring old data) is explicitly addressed in the link I posted. One would have to got out of their way to miss the point. And miss it entirely.
  - ilyt 3y ago
    theoretically possible is far away from practical. That's my point. It would take quite a bit of work to do even subset of what most other solutions come out of the box, at most likely much lower performance (the reason to use cache in first place). You can put a fucking text files on the disk as cache and `find -atime X -delete` to clear it, doesn't mean you should use it.
  - NavinF 3y ago
    That link just says "Use Postgres for caching instead of Redis with UNLOGGED tables". That's not helpful and going one link deeper, it says "reports range from 10% to more than 90% in speed gain" which is not that fast. > the SO link showing that Postgres cannot do caching (expiring old data) is explicitly addressed Nope, UNLOGGED tables don't expire old data. They just fill up forever unless you use a trigger like the one in the answer I linked. I also don't see anyone claiming they can saturate their network interface with postgres the same way they can with any KV store.
    - anarazel 3y ago
      > I also don't see anyone claiming they can saturate their network interface with postgres the same way they can with any KV store. I recently tested it, and I could trivially saturate a 10GBit interface with postgres. https://news.ycombinator.com/item?id=35296130 https://news.ycombinator.com/item?id=35296130
      - NavinF 3y ago
        With concurrent writes?
        anarazel 3y ago
        I'm sure there's a rate of concurrent writes where that wouldn't be true anymore, but if so, you're likely not going to be benefiting that much from the approach to caching.

You can use Postgres for caching, and many other things. https://www.amazingcto.com/postgres-for-everything/ https://www.amazingcto.com/postgres-for-everything/

ilyt 3y ago

Missing the point entirely

jmartrican 3y ago
I was responding to this comment. > I don't think it's even possible to use postgres as a traditional cache. The link I posted shows that you can use Postgres as a traditional cache. Specifically, the SO link showing that Postgres cannot do caching (expiring old data) is explicitly addressed in the link I posted. One would have to got out of their way to miss the point. And miss it entirely.
- ilyt 3y ago
  theoretically possible is far away from practical. That's my point. It would take quite a bit of work to do even subset of what most other solutions come out of the box, at most likely much lower performance (the reason to use cache in first place). You can put a fucking text files on the disk as cache and `find -atime X -delete` to clear it, doesn't mean you should use it.
- NavinF 3y ago
  That link just says "Use Postgres for caching instead of Redis with UNLOGGED tables". That's not helpful and going one link deeper, it says "reports range from 10% to more than 90% in speed gain" which is not that fast. > the SO link showing that Postgres cannot do caching (expiring old data) is explicitly addressed Nope, UNLOGGED tables don't expire old data. They just fill up forever unless you use a trigger like the one in the answer I linked. I also don't see anyone claiming they can saturate their network interface with postgres the same way they can with any KV store.
  - anarazel 3y ago
    > I also don't see anyone claiming they can saturate their network interface with postgres the same way they can with any KV store. I recently tested it, and I could trivially saturate a 10GBit interface with postgres. https://news.ycombinator.com/item?id=35296130 https://news.ycombinator.com/item?id=35296130
    - NavinF 3y ago
      With concurrent writes?
      - anarazel 3y ago
        I'm sure there's a rate of concurrent writes where that wouldn't be true anymore, but if so, you're likely not going to be benefiting that much from the approach to caching.