<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Database-Performance on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/database-performance/</link>
		<description>Recent content in Database-Performance on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 26 Jul 2026 18:40:00 +0200</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/database-performance/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>PostgreSQL Indexes: Types, Tradeoffs, and Query Verification</title>
				<link>https://www.compilemymind.com/posts/postgresql-indexes-types-tradeoffs-query-verification/</link>
				<pubDate>Mon, 20 Jul 2026 17:34:55 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/postgresql-indexes-types-tradeoffs-query-verification/</guid>
				<description>&lt;p&gt;“Add an index” is incomplete advice. A useful PostgreSQL index must match:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;the operators in a real query;&lt;/li&gt;&#xA;&lt;li&gt;the order and selectivity of its predicates;&lt;/li&gt;&#xA;&lt;li&gt;any required ordering;&lt;/li&gt;&#xA;&lt;li&gt;the distribution and physical layout of production-like data; and&lt;/li&gt;&#xA;&lt;li&gt;the write, storage, and maintenance budget.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The planner is free to ignore an index when a sequential scan is cheaper. Your goal is not to force an index icon into &lt;code&gt;EXPLAIN&lt;/code&gt;; it is to reduce total workload cost.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
