Smart Read Replica for Postgres.
Early Access (AWS): https://t.co/5gI2sClAew
Community: https://t.co/2KP69gQ4yspgcache.com Los Angeles, CAJoined April 2026
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!
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.
We see a third path for scaling reads on PostgreSQL
Path 1 - Read replicas & server upgrades.
Path 2 - External caches.
Path 3 - CDC-driven smart read replicas.
We saw what's possible with PostgreSQL Logical Replication, and thought "it doesn't have to be this complicated."
@HuluWZ built an independent PgCache benchmark with a custom ecomm workload and some slick design choices.
No diff on point lookup speed (not our focus)...
But he saw 2.9 seconds -> 0.6 ms on a 10M-row join 🔥
dev.to/huluwz/how-i-p…
Independent benchmark of PgCache.
16M rows, published in full.
No difference for point lookups, because that's not what we're solving for (0.3ms → 0.3ms).
But the 10M-row join?
2.9s → 0.6ms
Unpaid, unaffiliated, MIT repo:
dev.to/huluwz/how-i-p…
In the age of Logical Replication there's simply no reason a human or agent should have to manually configure invalidation, TTLs ... much less decide which queries get cached.
PgCache does it all for you. Check out our benchmark harness.
github.com/PgCache/pgcach…
James did some benchmarking, with very interesting results that we shared out last week.
But don't take our word for it, here's the harness he used. Take it for a spin, let us know what you think!
github.com/PgCache/pgcach…
our talk is today at 9AM PT!
Come for the Logical Replication vibes ...
Stay for the surprising benefits of caching PostgreSQL data, instead of results!
meetup.com/postgres-meetu…
Some updates to the PgCache website: pgcache.com
check it out!
👉and don't forget to sign up for our talk tomorrow: Postgres Meetup for All: "Logical Replication is for more than ETL: building PgCache" 9AM PT / 4PM UTC
meetup.com/postgres-meetu…
"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 📆
Next Wednesday August 19th Postgres Meetup for All is hosting @PgCache . As always we'll have a recorded presentation followed by non-recorded open discussion. Join us!
meetup.com/postgres-meetu…
When we started PgCache, the goal was: Build an easier cache for Postgres.
Didn't expect folks to be so interested with how we're using PostgreSQL Logical Replication to do that.
Join us on 8/19 at 9AM PT on Postgres Meetup for All for the inside scoop:
meetup.com/postgres-meetu…
The founding team will be presenting on PgCache at Postgres Meetup for All 🐘
Wednesday, August 19 at 9AM PST / 12PM EST.
- current status
- how we got started, and
- surprising discoveries from a year building on PostgreSQL
signup here: meetup.com/postgres-meetu…
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.
Our friend Kate Gawron built a white-label demand response app for a hackathon, and threw PgCache into the stack.
Five grid operators, multi-tenant across four countries, and 489 unit tests is not too shabby for a hackathon build!
kategawron.co.uk/2026/06/i-buil…
PgCache doesn't just relay data to users: it keeps a conversation going with origin.
I don't know of anyone else doing this for Postgres
full blog post👇
pgcache.com/blog/postgres-…
@devXritesh It's a trick question. First tidy up your db before adding complexity to your stack (internals, indexes, proper SQL, etc).
Second, and only if needed, put PgCache on there because (a) Redis = work (logic, invalidation, maintenance) and (b) Full Read Replica = overkill.
24 Followers 49 FollowingTech Enthusiast
Sports Fanatic
🛠️ Building structural solutions in the middle of chaos
Poet when the correct inspiration strikes
1K Followers 5K FollowingFrontend Dev / Geminiana (seja lá oque isso significa) / lolzeira nas horas vagas / (She/her ) / and a grown woman, I can do whatever I want.
2K Followers 20 FollowingEnable 🖖 DB branching and ⚡️ thin cloning for *any* Postgres database and empower DB testing in CI/CD. GitHub ⭐️👍 https://t.co/onPmk55KZs
656 Followers 3 FollowingA visualisation tool for Postgres explain analyze that also gives performance advice. Tweets by @michristofides. Status: https://t.co/GJ9y10JP41
15K Followers 2K FollowingArtificially inteligent | CEO @softodev | Delivering custom software & applied AI for real results | Redefining software dev in the AI era | Ride along!
1K Followers 5K FollowingFrontend Dev / Geminiana (seja lá oque isso significa) / lolzeira nas horas vagas / (She/her ) / and a grown woman, I can do whatever I want.