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

Поиск
Список
Период
Сортировка
От Stephen Samuel (Sam)
Тема Re: Trying to understand why a query is filtering when there is a composite index
Дата
Msg-id CANRyZ7Yn2-LZ4Rx8B1RdAqX9DdQhCgVVhx_-HB9i5xg5V26QQg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Trying to understand why a query is filtering when there is a composite index  (Peter Geoghegan <pg@bowt.ie>)
Ответы Re: Trying to understand why a query is filtering when there is a composite index
Список 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@bowt.ie> wrote:
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 every row,.

This has been fixed for Postgres 17:

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

--
Peter Geoghegan

В списке pgsql-performance по дате отправления: