PG Mood Ring is a one-tap PostgreSQL incident tracker and on-call journal. “PG” means PostgreSQL. Every time production bites — a deadlock, replication lag, a connection storm, vacuum bloat, disk full, an out-of-memory kill, a rogue query, or a broken extension — you log it in a single tap and quietly build a private monthly record of what you actually handled, how you solved it, and which runbooks you’re missing.
Yes — it’s free and there’s no signup. Your on-call log lives only in your browser’s local storage, and you can export a JSON backup anytime.
Common failure modes — deadlocks, replication lag, connection storms, vacuum/bloat, disk full, out-of-memory, rogue queries, idle-in-transaction and broken extensions — plus free-text SQLSTATE codes and the specific extension that failed.
Only a small pseudonymous signal when the live feed is on: failure type + platform + UTC day, tied to a random per-device id. No name, no query text, no notes. We also count one anonymous daily visit (that same id + the day, no incident attached) so we can see returning vs new engineers. The one exception is the short text under “Something Else,” shared anonymously to help add new categories.
The community mood gets you through the door; your own monthly journal is the reason to return. After a few weeks it shows what you keep firefighting and where your documentation is weak.
Haider Z vibe-coded this experiment.
By day I wrangle PostgreSQL in production and write The Sev-1 Database — a newsletter of PostgreSQL insights, deep dives, and hard-won engineering lessons. PG Mood Ring is the playful front door; the newsletter is where the real incident write-ups and troubleshooting live.