Have a local agent watch Postgres or MySQL for slow-query regressions
After years of reactive DBA work, the ReadySet team built RDST, an always-on local agent that watches database stats for slow queries and missing or harmful indexes, so problems are caught before the database falls over.
Source
gvsg on Hacker News · 2026-10-15 · Project link
Written in our own words. Credit to the original author. Link checked 2026-10-16.
What they did
After years of reactive DBA work, the ReadySet team built RDST, an always-on local agent that watches database stats for slow queries and missing or harmful indexes, so problems are caught before the database falls over.
Result (as claimed)
Open source on GitHub; 6 points on Show HN.
Tools they used
Cost: Pricing depends on the tools you pick; check each official pricing page.
Set it up
Pick a contained repo or task
Start on a branch or side project where mistakes are cheap.
Install and configure
Set up Postgres, MySQL. Read what it can run on your machine and limit permissions where possible.
Run it on a real task
Give it a well-scoped issue and let it work. Review the diff like any pull request.
Add guardrails
Keep tests and CI in the loop, and never let an agent push to main or touch production secrets unattended.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: Have a local agent watch Postgres or MySQL for slow-query regressions What the original author did: After years of reactive DBA work, the ReadySet team built RDST, an always-on local agent that watches database stats for slow queries and missing or harmful indexes, so problems are caught before the database falls over. Reported result (as claimed by the author): Open source on GitHub; 6 points on Show HN. Source: https://news.ycombinator.com/item?id=50107729 Tools they used: Postgres, MySQL Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: Have a local agent watch Postgres or MySQL for slow-query regressions What the original author did: After years of reactive DBA work, the ReadySet team built RDST, an always-on local agent that watches database stats for slow queries and missing or harmful indexes, so problems are caught before the database falls over. Reported result (as claimed by the author): Open source on GitHub; 6 points on Show HN. Source: https://news.ycombinator.com/item?id=50107729 Tools they used: Postgres, MySQL Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: Have a local agent watch Postgres or MySQL for slow-query regressions What the original author did: After years of reactive DBA work, the ReadySet team built RDST, an always-on local agent that watches database stats for slow queries and missing or harmful indexes, so problems are caught before the database falls over. Reported result (as claimed by the author): Open source on GitHub; 6 points on Show HN. Source: https://news.ycombinator.com/item?id=50107729 Tools they used: Postgres, MySQL Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Related use cases
Run a self-hosted DBA agent for Postgres and MySQL
Built DeepSQL, a self-hostable DBA agent for Postgres and MySQL.
Manage agent sessions from your phone and watch
Built claude-master: all sessions in one view on phone and watch, reply by tap or voice, replies read aloud, live quota; even the demo video is code.
Build Otis, a minimal AI agent that runs local models out of the box
Shipped I built Otis, a minimal AI agent that runs local models out of the box and shared it as a Show HN.
Let an agent watch user sessions, find real bugs and open verified fixes
Opslane is an open-source agent that spots user-facing issues from sessions, investigates them and only opens a pull request when it can verify the fix, built after years of bug-bash backlogs at Robinhood.