PgCache · Oct 29, 2026 · 7:48 PM UTC

PgCache

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.

PgCache · Oct 23, 2026 · 7:58 PM UTC

PgCache@PgCacheOct 23

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 😎

PgCache · Oct 9, 2026 · 5:55 PM UTC

PgCache@PgCacheOct 9

transactions now supported 👇

PgCache · Sep 25, 2026 · 3:17 PM UTC

PgCache@PgCacheSep 25

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."

PgCache · Sep 21, 2026 · 8:13 PM UTC

PgCache@PgCacheSep 21

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.

123

PgCache · Sep 16, 2026 · 9:28 PM UTC

PgCache@PgCacheSep 16

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!

PgCache · Sep 10, 2026 · 3:27 PM UTC

PgCache@PgCacheSep 10

Don't wonder if caching might help. Find out. Takes < 1 min (locally in browser via WebAssembly). Check it out at pgcache[.]com/fit

PgCache · Sep 9, 2026 · 4:31 PM UTC

PgCache@PgCacheSep 9

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.

PgCache · Aug 17, 2026 · 3:00 PM UTC

PgCache@PgCacheAug 17

"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 📆

PgCache · Jul 30, 2026 · 4:21 PM UTC

PgCache@PgCacheJul 30

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.