Re: 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-23T00:50:56Z
Lists: pgsql-hackers
Attachments
- v1-0001-doc-Cross-reference-enable_indexscan-and-enable_inde.patch (text/x-patch) patch v1-0001
On Mon, Oct 21, 2024 at 7:20 PM David Rowley <dgrowleyml@gmail.com> wrote: > 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. > > Yeah, I agree. The documentation could better reflect the current > behaviour. > > Do you want to submit that in patch form? > > Went with a slightly different wording that seems to flow better with the xrefs I added between the two options. 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