PostgreSQL cache invalidation: the late-fill race
Walk through a cache-aside race where an old read refills a deleted key after commit. Understand publication fencing, snapshots, rollback and request-local caches.
Read articlePostgreSQL caching, in practice
Start with the work a request repeats. These articles connect PostgreSQL’s read path to application decisions: what to measure, how stale data gets published, and what a batch response must preserve.
New to the extension? Run the local demo, then use the caching decision guide to choose a read path.
Subscribe via AtomWhen a PostgreSQL row cache helps: measure the whole read
Design a fair PostgreSQL row-cache comparison using prepared SQL, SQL mget and RESP MGET. Separate warm reads, misses, batch sizes, writes and client costs.
Read articleBatch PostgreSQL reads without losing order or missing keys
Replace N+1 primary-key queries while preserving duplicate IDs, input order, NULL positions and missing rows. Compare ANY, WITH ORDINALITY and SQL mget.
Read article