<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Indexing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/indexing/</link>
    <description>Recent content in Indexing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/indexing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted PostgreSQL Index Optimization: HypoPG vs pg_qualstats vs pg_stat_user_indexes</title>
      <link>https://www.pistack.xyz/posts/2026-06-02-postgresql-index-optimization-hypopg-pgqualstats-pgstatindexes-guide/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-02-postgresql-index-optimization-hypopg-pgqualstats-pgstatindexes-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;PostgreSQL&amp;rsquo;s performance is heavily dependent on proper indexing. A single missing index can turn a millisecond query into a multi-second table scan, while unused indexes waste disk space, slow down writes, and bloat your buffer cache. For self-hosted PostgreSQL deployments, having the right tools to analyze, test, and optimize your index strategy is essential.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
