the daily mood of PostgreSQL production — log each incident in one tap and build a private on-call journal that gets more useful every month
—
⛅
…
…
…
🐘
…
🛠️ I run Postgres onpowers the platform comparison below
What fought your Postgres today? — tap once per occurrence (log it every time it happens)
📋 Today’s log — every occurrence you handled
Your on-call record
0
🔥 day streak
0
occurrences logged
0
signals today · global
Today's storm — what's breaking across the fleet
📇 On-call record — this month
📈 Last 30 days — trend
ℹ️ What is PG Mood Ring?
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.
1Tap what brokeLog each PostgreSQL incident the moment it happens — one tap, no forms, no login. It’s saved privately in your browser.
2Build your on-call journalYour month adds up automatically: top failure modes, how often docs were missing, what you leaned on AI for — a personal history that’s more useful the longer you use it.
3Read the fleet’s moodSee today’s live community storm feed — what’s breaking for other PostgreSQL engineers right now, counted as one anonymous signal per person, per failure type, per day.
Is PG Mood Ring free, and do I need an account?
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.
What PostgreSQL incidents can I track?
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.
What data leaves my device?
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. The one exception is the short text under “Something Else,” shared anonymously to help add new categories.
Why should I come back every day?
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.