How PgCache compares
PgCache is a caching proxy for Postgres. Some of the tools below take read load off Postgres in other ways. Others, like connection poolers, solve a different problem and can run alongside PgCache.
Read replicas
Other ways to cache Postgres reads
PgCache vs Redis
An in-memory data store used for caching, sessions, queues and more. PgCache covers one of those uses: caching Postgres query results.
Read more →PgCache vs Valkey
The Linux Foundation's fork of Redis, started in 2024. PgCache covers one of its uses: caching Postgres query results.
Read more →PgCache vs Amazon ElastiCache
AWS's managed Valkey, Redis OSS and Memcached service. PgCache caches RDS and Aurora Postgres reads.
Read more →PgCache vs Readyset
A caching proxy for Postgres and MySQL with two kinds of cache. PgCache is a caching proxy for Postgres with one.
Read more →Connection poolers that run alongside PgCache
PgCache and PgBouncer
A connection pooler for Postgres, first released by Skype in 2007. PgCache serves repeated reads and can run in front of it.
Read more →PgCache and PgDog
A pooler, load balancer and sharding proxy for Postgres, started in 2024. PgCache serves repeated reads and can run in front of it.
Read more →See how this applies to your database
The Fit Analyzer reads a pg_stat_statements export in your browser and shows which of your queries PgCache would serve. Questions are welcome at [email protected].