PgCache (@PgCache) header
PgCache (@PgCache) profile picture

PgCache

@PgCache

The drop-in Postgres cache. Check your workload: https://nitter.cf/t.co/WkdtkZP5G8 Quick start: https://nitter.cf/t.co/zEEzsoPPoR Discord: https://nitter.cf/t.co/2KP69gQ4ys

 Los Angeles, CA
pgcache.com
Joined April 2026
  • Tweets83
  • Following62
  • Followers17
Nobody who got close to trying PgCache this year held off over speed. Mostly it was stale data, which is interesting, since lots of teams already read from a replica that lags the primary. If that's you, here's a first step: test PgCache on the reads you send to a replica.
A psql terminal window. The query SELECT replay_lag FROM pg_stat_replication returns one row: 00:00:00.284153. Below it, SQL comments read: "a replica 0.3 s behind: totally normal." "a cache fed by replication: wait, what about stale data?" "fair question. more in the post." Footer: PgCache, smart read replica for Postgres.

ALT A psql terminal window. The query SELECT replay_lag FROM pg_stat_replication returns one row: 00:00:00.284153. Below it, SQL comments read: "a replica 0.3 s behind: totally normal." "a cache fed by replication: wait, what about stale data?" "fair question. more in the post." Footer: PgCache, smart read replica for Postgres.

6
PgCache 0.8.0 is out! @leonardobenedet, one of our design partners, benchmarked it the day after release. On a complex multi-tenant dashboard it served 24x the requests per second of Postgres alone at 100 tenants, and was still 1.5x ahead at 1,000 😎
Image from PgCache (@PgCache)
2
45
transactions now supported 👇
Image from PgCache (@PgCache)
7
Which Postgres queries are worth caching? We shared a free online Postgres tool on Reddit yesterday. 26k views and 180 shares so far! The idea behind it is pretty simple: rank your queries by total time vs what "feels slow."
Image from PgCache (@PgCache)
1
1
18
Already decided Postgres needs a cache? You don't have to build it into your app. PgCache sits between your app and Postgres and caches your hot reads. Swap the connection string. No cache code, no TTL to guess at.
Image from PgCache (@PgCache)
1
1
1
123
We built PgCache but we've never met (yet!) That'll change when we head to NYC in a couple weeks for Postgres Summit US/ @pgconfnyc And, if you're in SoHo 9/30 to 10/2, and want to grab a coffee, send us DM --we'd love to connect!
Image from PgCache (@PgCache)
2
44
Don't wonder if caching might help. Find out. Takes < 1 min (locally in browser via WebAssembly). Check it out at pgcache[.]com/fit
1
2
28
You probably don't need another read replica. What you probably need is the answer to this question: "how much of our read traffic can be cached?" Check yours for free in 2 minutes, locally in your browser, at pgcache [dot] com/fit.
Image from PgCache (@PgCache)
1
15
"Logical replication is for more than just ETL" If PostgreSQL replication, caching, and optimization are things you pay attention to... ...then consider this is a friendly neighborhood reminder to block off Wednesday 8/19, 9am PT / 4PM UTC 📆
Image from PgCache (@PgCache)
1
2
14
2 vCPU PgCache in front of RDS, 27M rows of Stack Exchange data. read-only: origin CPU 70% to 3%. throughput 5-6x. p50 15ms to 2.5ms. If you're running a heavy read-only workload on Postgres and want to make things easier for origin ... DM me.
Image from PgCache (@PgCache)
20
Caching is a bit of a cognitive monolith All of Read Optimization is But we're making it better. The goal: You never have to think about your optimization layer again. thereadreplica.com/news/logi…
Image from PgCache (@PgCache)
1
1
17
The whole way that we've been trained to think about read optimization is broken. Since PostgreSQL 10 and the introduction of Logical Replication, there's no good reason that most people running PostgreSQL at scale should have to think about read optimization
🤖 Made with AI
Image from PgCache (@PgCache)
1
7
Load more