Postgres Pro
Downloads
Home   >   mailing lists

Re: Trying to understand why a query is filtering when there is a composite index - Mailing list pgsql-performance

From Peter Geoghegan
Subject Re: Trying to understand why a query is filtering when there is a composite index
Date
Msg-id CAH2-WznVMvKQaT92HgxQ4T_SUOmGezSiFFCdwM3PL90g+5xCbA@mail.gmail.com
Whole thread Raw
In response to Trying to understand why a query is filtering when there is a composite index  ("Stephen Samuel (Sam)" <sam@sksamuel.com>)
Responses Re: Trying to understand why a query is filtering when there is a composite index
List pgsql-performance
Tree view 
On Sun, Aug 18, 2024 at 9:56 PM Stephen Samuel (Sam) <sam@sksamuel.com> wrote:
> My question is, why isn't it using the index for column b? Is this expected? And why is it doing heap lookups for
everyrow,. 

This has been fixed for Postgres 17:

https://pganalyze.com/blog/5mins-postgres-17-faster-btree-index-scans

--
Peter Geoghegan

pgsql-performance by date:

Previous
From: "Stephen Samuel (Sam)"
Date:
Subject: Trying to understand why a query is filtering when there is a composite index
Next
From: "Stephen Samuel (Sam)"
Date:
Subject: Re: Trying to understand why a query is filtering when there is a composite index