<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Your first check on kbdiag</title><link>https://kevin-wenyu.github.io/kbdiag-docs/docs/get-started/</link><description>Recent content in Your first check on kbdiag</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 27 Sep 2026 13:49:17 +0800</lastBuildDate><atom:link href="https://kevin-wenyu.github.io/kbdiag-docs/docs/get-started/index.xml" rel="self" type="application/rss+xml"/><item><title>Read a real result</title><link>https://kevin-wenyu.github.io/kbdiag-docs/docs/get-started/reading-results/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kevin-wenyu.github.io/kbdiag-docs/docs/get-started/reading-results/</guid><description>&lt;p&gt;Captured on 2026-09-27 (UTC+08) on a local KingbaseES V008R006C009B0014 primary, database &lt;code&gt;test&lt;/code&gt;, using &lt;code&gt;~/kbdiag&lt;/code&gt; built from Go source commit &lt;code&gt;93bf65d&lt;/code&gt; (static linux/amd64 binary). This is lab evidence, not production validation. PIDs, counts and timings belong to this capture only. The idle-in-transaction session was created by a fault-injection script. The warning threshold was lowered to 5 seconds with &lt;code&gt;--idle-in-txn-warn 5&lt;/code&gt; so the example did not have to wait the default 300.&lt;/p&gt;</description></item></channel></rss>