PgCache 🐘🦀 @pgcache.bsky.social · 25/09/2026Which 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." 100
PgCache 🐘🦀 @pgcache.bsky.social · 21/09/2026Already 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. See if your workload fits: pgcache.com/fit #PostgreSQL 000
PgCache 🐘🦀 @pgcache.bsky.social · 16/09/2026We built PgCache but we've never met (yet!) That'll change when we head to NYC in a couple weeks for @pgsummitus.bsky.social 🎉🐘 If you're in SoHo 9/30 to 10/2, and want to grab a coffee, send us DM and we'd love to connect! 000
PgCache 🐘🦀 @pgcache.bsky.social · 10/09/2026Don't wonder if caching might help. Find out. Takes < 1 min (locally in browser via WebAssembly). Check it out at pgcache[.]com/fit 000
PgCache 🐘🦀 @pgcache.bsky.social · 09/09/2026You 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. 000
PgCache 🐘🦀 @pgcache.bsky.social · 17/08/2026"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 join us on Wednesday 8/19 at 9am PT / 4PM UTC 🦀🐘⚡ 010
PgCache 🐘🦀 @pgcache.bsky.social · 30/07/20262 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. 000
PgCache 🐘🦀 @pgcache.bsky.social · 26/06/2026Caching is a bit of a cognitive monolith All of read optimization is. People don't think about it, deeply. They just default to full read replicas, or redis. We're making it better. The goal: You never have to think about your optimization layer again. www.thereadreplica.com/news/logical... 000
PgCache 🐘🦀 @pgcache.bsky.social · 22/06/2026The 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 000
PgCache 🐘🦀 @pgcache.bsky.social · 19/06/2026We 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. www.pgcache.com/blog/postgre... 020
PgCache 🐘🦀 @pgcache.bsky.social · 27/05/2026no middle gear in most postgres stacks today. you either run a full read replica or you don't. nothing in between. most teams need the in-between: scale without paying to duplicate every cold table. what am i missing? 000
PgCache 🐘🦀 @pgcache.bsky.social · 14/05/2026a traditional read replica copies your whole database because it has no idea what you actually read. a smart one watches the query traffic and caches what gets hit. WAL stream handles invalidation ; no TTLs, no stale window, no tuning. the shape of your traffic, not the shape of your schema. 010
PgCache 🐘🦀 @pgcache.bsky.social · 13/05/2026my postgres read replica bill, itemized: data I actually query ✓ tables from 2022 I forgot exist ✓ deprecated user_sessions table ✓ 6 months of audit logs ✓ cold data that hasn't been touched since the last oncall incident ✓ you replicate all of it. every time. to serve 20% of your reads. 010
PgCache 🐘🦀 @pgcache.bsky.social · 06/05/2026AWS read replicas are expensive because they copy everything to serve a small fraction of reads. PgCache is a smart read replica that caches only hot data, stays in sync via CDC, and can reduce IOPS by 40–60%. Free trial. Free small instance. Deploy in minutes. 110
PgCache 🐘🦀 @pgcache.bsky.social · 05/05/2026Stop scaling Postgres with brute force. Read replicas copy 100% of your data for a fraction of queries...and add real ops overhead. PgCache: cache the hot 20% that matters. #PostgreSQL #SRE 231
PgCache 🐘🦀 @pgcache.bsky.social · 30/04/2026Stop wasting money replicating 100% of your Postgres DB just to serve the hot 20% of your data. 💸 PgCache is a "Pareto Replica" proxy that uses CDC for real-time sync. No stale TTLs, no app rewrites. 110
PgCache 🐘🦀 @pgcache.bsky.social · 24/04/2026Smart DBAs are ditching read replicas and crazy IOPS bills. DM to learn more. ... or try it for yourself on our AWS AMI (v0.4.8): aws.amazon.com/marketplace/... 000
PgCache 🐘🦀 @pgcache.bsky.social · 22/04/2026When you realize you could be getting more out of PostgreSQL with an automated caching proxy 000
PgCache 🐘🦀 @pgcache.bsky.social · 22/04/2026If you’re scaling cloud Postgres and still adding read replicas… you’re doing it the hard way. PgCache auto-caches ~80% of queries via proxy. No app changes. No invalidation drama (CDC handles it). Some of what we support 👇 Reply "FULL" and I'll send you the full list 110
PgCache 🐘🦀 @pgcache.bsky.social · 20/04/2026Scaling database teams don’t need more cache complexity. They need a way to shape database load, effortlessly. PgCache = no app changes CDC-fresh cache 80% of common query patterns covered automatically Less babysitting. More control. DM to see if we fit your stack. 110
PgCache 🐘🦀 @pgcache.bsky.social · 17/04/2026(3/3) Get early, discounted access to PgCache on AWS marketplace before May 1, 2026: www.pgcache.com/register/pil... More info & docs: www.pgcache.com (here's what we currently cache automatically 👇) 000
PgCache 🐘🦀 @pgcache.bsky.social · 09/04/2026Postgres deserves a better read cache. We're testing PgCache, our Postgres-only cache that acts like a transparent proxy. Drop-in, auto-refresh, dead simple to deploy. If this sounds useful, join the waitlist: pgache.com#waitlist 000