>I personally wouldn't like to put caching in Postgres, even though it would work at lower scales.

Probably should stop after this line - that was the point of the article. It will work at lower scales. Optimize later when you actually know what to optimize.

My point is more that at that scale I'd try to avoid caching entirely. Unless you're doing analytical queries over large tables, Postgres is plenty fast without caching if you're not doing anything stupid.