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@xxxxxxx> wrote:
On Sun, Aug 18, 2024 at 9:56 PM Stephen Samuel (Sam) <sam@xxxxxxxxxxxx> 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
