Re: Why isn't PG using an index-only scan?

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Jean-Christophe BOGGIO <postgresql(at)thefreecat(dot)org>
Cc: "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: Why isn't PG using an index-only scan?
Date: 2025-09-18 11:32:01
Message-ID: CAApHDvrQxSO8SJGHqiRuhuSacy5idavz4EkKKfW76qaELHKSOg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, 18 Sept 2025 at 19:45, Jean-Christophe BOGGIO
<postgresql(at)thefreecat(dot)org> wrote:
> Ok but then why is it doing it on the AD table? Is it because of the
> number of rows?

It's hard to tell as I don't have a clear view on which columns are
from which tables. Perhaps "ad" can Index Only Scan because all of
the columns required are in an index but with "oeu" there's a column
being used that's not indexed?

David

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message David Rowley 2025-09-18 11:35:34 Re: Why isn't PG using an index-only scan?
Previous Message Andrei Lepikhov 2025-09-18 07:55:57 Re: Why isn't PG using an index-only scan?