| 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-22 02:40:11 |
| Message-ID: | CAKFQuwaC6E02tnDKFzf4CWhpjJYAv4XfZoMuBn_a07QnYeRb1Q@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 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?
>
Will do tomorrow.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2024-10-22 02:54:39 | Re: Better error reporting from extension scripts (Was: Extend ALTER OPERATOR) |
| Previous Message | David Rowley | 2024-10-22 02:20:22 | Re: EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on |