Hacker News Reader

Unfortunately that's just how postgres works? I thought the rule of thumb is still to allocate 25% of memory for postgres 's shared buffer, and 50% of memory for OS buffer cache (i.e. ARC when using ZFS)?

View on HN

That’s how postgres works, but ZFS lets you work around that by disabling arc caching on a dataset by dataset basis.

>Unfortunately

No, postgres know better what to cache then arc.

For a transaction processing workload (where hitting indexes is the all-important thing), that's exactly right. But if you have more of an analytic workload involving sequential scans, Postgres definitely expects the underlying storage system to be handling at least some of the caching.

Reply on news.ycombinator.com