<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Sql on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/sql/</link>
		<description>Recent content in Sql on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 20 Jul 2026 17:34:55 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/sql/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;A PostgreSQL index is useful when its access method and column ordering support a real query predicate, ordering requirement, or constraint at an acceptable maintenance cost. Adding an index does not force the planner to use it, and an index that speeds one read can increase storage, write amplification, vacuum work, and planning choices. Selection therefore begins with the query and data distribution, then ends with measured plans and operational observation.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
