| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(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-22 02:20:22 |
| Message-ID: | CAApHDvr_Ncavgr7z4xmXuStWCaQoE0=z2kZj6JiFku8DB1iBfw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 22 Oct 2024 at 14:46, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> 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.
Yeah, I agree. The documentation could better reflect the current behaviour.
Do you want to submit that in patch form?
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-10-22 02:40:11 | Re: EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on |
| Previous Message | David G. Johnston | 2024-10-22 01:46:23 | EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on |