Karthik M

I run DBExplore, a Singapore company building Postgres Autopilot: one control plane for every Postgres a team runs, where agents observe, detect, advise and act, and where acting is something a rule has to be allowed to do rather than something it simply does.

The posts here are the working notes behind that. What a query plan is worth storing and what can be thrown away. Where a managed engine's metrics stop describing what the application sees. What a major-version upgrade check does not check. They are written the way I would explain a problem to the person who has to carry the pager for it, which means the trade-off we chose is in the post rather than left out of it.

I write about Postgres only, and about our own product sparingly. If something here is wrong, or right in a way that cost you an outage first, I would like to hear it: hello@dbexplore.com, or through the contact page.