Re: Trying to understand why a query is filtering when there is a composite index

From: "Stephen Samuel (Sam)" <sam(at)sksamuel(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Trying to understand why a query is filtering when there is a composite index
Date: 2024-08-19 02:01:16
Message-ID: CANRyZ7Yn2-LZ4Rx8B1RdAqX9DdQhCgVVhx_-HB9i5xg5V26QQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Oh as simple as upgrading!
Ok great, appreciate the quick reply. Will have to wait for AWS to support
17 :)

On Sun, 18 Aug 2024 at 20:59, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:

> On Sun, Aug 18, 2024 at 9:56 PM Stephen Samuel (Sam) <sam(at)sksamuel(dot)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 every row,.
>
> This has been fixed for Postgres 17:
>
> https://pganalyze.com/blog/5mins-postgres-17-faster-btree-index-scans
>
> --
> Peter Geoghegan
>

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Peter Geoghegan 2024-08-19 02:08:24 Re: Trying to understand why a query is filtering when there is a composite index
Previous Message Peter Geoghegan 2024-08-19 01:59:10 Re: Trying to understand why a query is filtering when there is a composite index