Why PostgreSQL Ignores Your Index (Sometimes), Entry #2

<p><em>B-tree internals, column order and planner statistics in Postgres 19, checked against MongoDB's ESR rule.</em></p> <p>Most "add an index" advice stops at <code>CREATE

<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

<p>When we write:<br /> </p> <div class="highlight js-code-highlight"> <pre class="highlight sql"><code><span class="k">SELECT</span> <span class="o">*</span> <span

<p><strong>TL;DR:</strong> Postgres has <code>pg_stat_user_indexes</code>. It tells you how many times each index was scanned. It does <em>not</em> tell you whether the slow query

<p>Hello, I'm Tuan.</p> <p>When backend engineers encounter a slow query, the first instinct is often something like:</p> <blockquote> <p>"Check the WHERE and ORDER BY, then just

<p>PROFESSIONAL DJANGO ENGINEERING SERIES #6</p> <blockquote> <p>If you have never read a query execution plan, you are flying blind on database performance. Here is how to read

<h1> Prisma query logging y PostgreSQL: dónde termina el ORM y empieza la base </h1> <p>Activé query logging en Prisma, vi los queries llegando a la consola, y asumí que tenía

<p>At 2:14 PM on a Tuesday in Q3 2024, our production PostgreSQL 16 cluster hit a p99 query latency of 2.8 seconds for our core order lookup endpoint, triggering 12 customer