Re: EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Melanie Plageman <melanieplageman@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>, Robert Haas <robertmhaas@gmail.com>
Date: 2024-10-22T02:20:22Z
Lists: pgsql-hackers
On Tue, 22 Oct 2024 at 14:46, David G. Johnston <david.g.johnston@gmail.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
Commits
-
Doc: clarify enable_indexscan=off also disabled Index Only Scans
- 857f13f79994 12.21 landed
- ee8db41a9432 13.17 landed
- ca643bcd7a81 14.14 landed
- 75f09cc460a3 15.9 landed
- 4f47ee03d5f8 16.5 landed
- e5086b3ff441 17.1 landed
- dda781609f97 18.0 landed