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: | EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on |
Date: | 2024-10-22 01:46:23 |
Message-ID: | CAKFQuwYx0m2O3rM=CF1nj6xuqNMTe-NPNOsue7chyqS_EjhKng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Monday, October 21, 2024, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> On Tue, 22 Oct 2024 at 13:45, Melanie Plageman
> <melanieplageman(at)gmail(dot)com> wrote:
> > I was surprised today when I saw that with
> > enable_indexscan=off
> > enable_indexonlyscan=on
>
> Robert did propose to change this behaviour while he was working on
> the disabled_nodes changes. I did push back on the proposed change
> [1]. If you feel strongly that what we have is wrong, then maybe it's
> worth opening the discussion about that again.
>
We should probably at least improve the documentation in 19.17.1; this
interaction is apparently not self-evident.
enable_indexscan
Enable or disable the planner’s use of both index-scan and index-only-scans
plan types.
enabled_indexonlyscan
Set to off to disable index-only-scan plan type while leaving index-scan
plan types enabled. This setting has no effect if enable_indexscan is set
to off.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2024-10-22 02:20:22 | Re: EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on |
Previous Message | David Rowley | 2024-10-22 01:32:45 | Re: EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on |