transactions now supported 👇

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

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.

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!

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

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.

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

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.

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…

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