Documentation

PgCache is a transparent caching proxy for PostgreSQL. Point your application at PgCache instead of your origin database — no code changes — and it caches query results and keeps them consistent with the origin through logical replication.

New here? Start with Getting Started to get a proxy running in a few minutes, then read How Caching Works to understand what gets cached and the consistency model. The Configuration and Compatibility references cover every setting and which query patterns are cached.

Get started

Getting Started Install PgCache via Docker, configure your origin database, and verify caching is working.

Concepts

How Caching Works Understand PgCache's caching architecture: what gets cached, how invalidation works, and consistency guarantees.

Reference

Configuration Complete reference for PgCache configuration: TOML file, CLI arguments, and Docker environment variables. Compatibility Supported PostgreSQL versions, query patterns, client libraries, and known limitations. Monitoring Set up Prometheus metrics, understand available metrics, and configure alerts for PgCache. Telemetry What anonymous telemetry PgCache collects, why, and how to disable it.

Operations

Operations Running PgCache in production: restart and recovery behavior, the replication slot lifecycle, cache warm-up, and high availability.

Deploy

Docker Deploy PgCache with Docker: Compose setups, mounting configuration and TLS certificates, health checks, restart policy, and resource sizing. AWS Marketplace Deploy PgCache from the AWS Marketplace AMI: store credentials in SSM, launch an instance, and connect your application.

Changelog

Changelog Release history and changes for PgCache.