<?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 Nalar</title>
    <link>https://nalar.dev/tags/indexing/</link>
    <description>Recent content in Indexing on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/indexing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Use Partial Indexes to Index the Rows You Actually Query</title>
      <link>https://nalar.dev/use-partial-indexes-to-index-the-rows-you-actually-query/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/use-partial-indexes-to-index-the-rows-you-actually-query/</guid>
      <description>&lt;p&gt;A normal database index contains an entry for every table row that qualifies for the indexed columns. That is often appropriate, but some applications repeatedly query only a small, stable subset of a table.&lt;/p&gt;&#xA;&lt;p&gt;Consider a task table where most tasks eventually become completed or archived, while the application dashboard mainly reads current open tasks. A full index on &lt;code&gt;project_id&lt;/code&gt; keeps index entries for historical rows even though those rows are rarely part of the hot query path.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
