<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Databases on vrajat</title><link>https://vrajat.com/tags/databases/</link><description>Recent content in Databases on vrajat</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 28 Jun 2026 11:30:00 +0530</lastBuildDate><atom:link href="https://vrajat.com/tags/databases/index.xml" rel="self" type="application/rss+xml"/><item><title>Agents Should Triage Postgres Through Runbooks</title><link>https://vrajat.com/posts/agents-postgres-triage-runbooks/</link><pubDate>Sun, 28 Jun 2026 11:30:00 +0530</pubDate><guid>https://vrajat.com/posts/agents-postgres-triage-runbooks/</guid><description>&lt;p>In database triage, the workflow can be represented as a Directed Acyclic Graph (DAG) of checks rather than a flat, linear script. Navigating this graph requires gathering data from a hierarchy of sources: logs, query statistics, active sessions, and execution plans. Based on the evidence a specific edge has to be traversed to the next investigation task.&lt;/p>
&lt;p>Running the wrong database command at the wrong time can saturate CPU or lock catalog tables or gather the wrong evidence. To safely automate triage, we must separate the mechanical tasks (codified in local tools) from the branching decisions (evaluated by the agent). The agent&amp;rsquo;s job is to navigate the path, not to execute arbitrary SQL.&lt;/p></description></item></channel></rss>