EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Melanie Plageman <melanieplageman@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>, Robert Haas <robertmhaas@gmail.com>
Date: 2024-10-22T01:46:23Z
Lists: pgsql-hackers
On Monday, October 21, 2024, David Rowley <dgrowleyml@gmail.com> wrote: > On Tue, 22 Oct 2024 at 13:45, Melanie Plageman > <melanieplageman@gmail.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.
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