Cookbook recipe

How shared_buffers and the OS page cache cooperate

Applies to PostgreSQL 13–17 Last reviewed May 2026 Grounded in source
Estimated investigation4 min

Scenario

You have two caches in front of disk — PostgreSQL's shared_buffers and the OS page cache. Knowing how they interact guides memory tuning. Diagnose it Check cache effectiveness: SELECT round(100*sum(blks_hit)/greatest(sum(blks_hit)+sum(blks_read),1),2) AS hit_pct FROM pg_stat_database; Why it…

Investigation Path

You have two caches in front of disk — PostgreSQL’s shared_buffers and the OS page cache. Knowing how they interact guides memory tuning.

Diagnose it

Check cache effectiveness:

SELECT round(100*sum(blks_hit)/greatest(sum(blks_hit)+sum(blks_read),1),2) AS hit_pct
FROM pg_stat_database;

Why it happens

PostgreSQL reads pages into shared_buffers; a miss there usually still hits the OS page cache (fast) before going to disk (slow). Both caches hold copies, so over-sizing shared_buffers can crowd out the OS cache.

This is a Pro lesson

Get every Learning Pathway and cookbook recipe — grounded in PostgreSQL source code, with diagnostics, fixes, and prevention for each topic.

Continue this lesson to learn:

  • How to fix it
  • Prevent it next time
  • Related & next steps
  • All 36 Learning Pathway lessons
  • 170+ cookbook recipes
  • Source-grounded diagnostics & fixes

Secure checkout Cancel anytime Source-grounded

Career Impact

This scenario builds production judgment and operational confidence under pressure.

Open Career Dashboard →

Keep going

Related & next steps

Was this helpful?

← All cookbook recipes