Thank you for the historical context and working, I understand what you were referring to before now.
Shayon > On Sep 24, 2024, at 2:08 PM, Peter Eisentraut <pe...@eisentraut.org> wrote: > > On 23.09.24 22:51, Shayon Mukherjee wrote: >> I am happy to draft a patch for this as well. I think I have a working >> idea so far of where the necessary checks might go. However if you don’t >> mind, can you elaborate further on how the effect would be similar to >> enable_indexscan? > > Planner settings like enable_indexscan used to just add a large number > (disable_cost) to the estimated plan node costs. It's a bit more > sophisticated in PG17. But in any case, I imagine "disabling an index" could > use the same mechanism. Or maybe not, maybe the setting would just > completely ignore the index.
