<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Performance on 免费白票</title>
    <link>https://dibi8.com/tags/performance/</link>
    <description>Recent content in Performance on 免费白票</description>
    <image>
      <title>免费白票</title>
      <url>https://dibi8.com/og-default.png</url>
      <link>https://dibi8.com/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 02 May 2026 10:00:00 +0800</lastBuildDate>
    <atom:link href="https://dibi8.com/tags/performance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Reading EXPLAIN ANALYZE in Postgres Without Getting Lost</title>
      <link>https://dibi8.com/posts/reading-explain-analyze-in-postgres-without-getting-lost/</link>
      <pubDate>Sat, 02 May 2026 10:00:00 +0800</pubDate>
      <guid>https://dibi8.com/posts/reading-explain-analyze-in-postgres-without-getting-lost/</guid>
      <description>EXPLAIN ANALYZE output looks intimidating until you know which three numbers actually matter. Here&amp;rsquo;s the order I read them in, and the patterns that point to specific bugs.</description>
    </item>
  </channel>
</rss>
