https://beh74.github.io/pgassistant-blog/tags/indexes/Recent content in Indexes on pgAssistant BlogHugo -- 0.147.0en-usMon, 11 May 2026 00:00:00 +0000https://beh74.github.io/pgassistant-blog/post/query_advisor/Mon, 11 May 2026 00:00:00 +0000https://beh74.github.io/pgassistant-blog/post/query_advisor/<p><img alt="Index Advisor" loading="lazy" src="https://beh74.github.io/pgassistant-blog/images/index_advisor_cover.png"></p> <p>PostgreSQL index design is often misunderstood.</p> <p>Many developers think that creating a good index simply means:</p> <blockquote> <p>“Create an index containing the columns from the WHERE clause.”</p></blockquote> <p>In reality, efficient index design is far more nuanced.</p> <p>The order of columns inside a composite index matters enormously, and the best choice depends on:</p> <ul> <li>Predicate types (<code>=</code>, <code>&gt;=</code>, <code>BETWEEN</code>, <code>LIKE</code>, etc.)</li> <li>Column selectivity</li> <li>Table size</li> <li>PostgreSQL planner statistics</li> <li>Actual execution plans</li> </ul> <p>This article explains the core principles behind efficient PostgreSQL index design before showing how pgAssistant automates this process using execution plans and database statistics.</p>