Re: EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Melanie Plageman <melanieplageman(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on
Date: 2024-10-29 01:40:50
Message-ID: CAKFQuwa6M_Hd0LX2xi3SPUvXaAqKCpn8Tnj6F=-jJZ9Avh0Chw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 28, 2024 at 3:54 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:

>
> I've attached that in patch form.
>
>
- Enables or disables the query planner's use of index-scan plan
- types. The default is <literal>on</literal>.
+ Enables or disables the query planner's use of index-scan and
+ index-only-scan plan types. The default is <literal>on</literal>.
+ Also see <xref linkend="guc-enable-indexonlyscan"/>.

I think the original wording "index-scan plan types" is what is confusing
me. The plural types is turning index-scan plan into a category of plans
rather than the single plan type "index scan".

Your proposed wording actually (accidentally?) fixes this because now the
plural types actually refers to two individual plan nodes, "index scan" and
"index-only scan".

The hyphenation still reads a bit odd but ok.

I am ok with this revision (and the patch as a whole) I suppose but I still
feel like something is missing here. Though probably that something would
fit better in an overview page rather than trying to get the settings to
explain all this to the reader.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2024-10-29 01:55:00 Re: Statistics Import and Export
Previous Message Andy Fan 2024-10-29 01:26:23 Re: detoast datum into the given buffer as a optimization.