PostgreSQL Caching: What It Does and What to Add
Postgres has no query cache, but it caches more than you think. What shared_buffers, plans, and the OS cache do, and which result cache to add.
Read more →Product updates, technical deep dives, and engineering insights.
Postgres has no query cache, but it caches more than you think. What shared_buffers, plans, and the OS cache do, and which result cache to add.
Read more →We bet early that the right way to cache Postgres was to do it in Postgres. Every hard problem we've encountered since then, that bet keeps paying us back.
Read more →A smart read replica keeps only the hot data your queries actually touch, instead of copying the whole database. Here is how PgCache decides what to keep.
Read more →Our license, and why we chose it.
Read more →Caching results is not the same as caching data. It's also harder. PgCache makes it easy.
Read more →PostgreSQL logical replication does transmit schema information via Relation messages, but only when data is modified, not when DDL executes. This timing makes it problematic for read replicas but perfectly suited for caching systems.
Read more →Examining how PostgreSQL's query optimizer has evolved from version 9.6 to 18.0, looking at three key SQL transformations.
Read more →Why we started PgCache and what we set out to build: transparent, CDC-driven caching for PostgreSQL. (Update: it shipped.)
Read more →