Re: On disable_cost

Robert Haas <robertmhaas@gmail.com> writes:
> What the patch does is: if you set either enable_indexscan=false or
> enable_indexonlyscan=false, then the corresponding path type is not
> generated, and the other is unaffected. To me, that seems like the
> logical way to clean this up.

> One could argue for other things, of course. And maybe those other
> things are fine, if they're properly justified and documented.

[ shrug... ]  This isn't a hill that I'm prepared to die on.
But I see no good reason to change the very long-standing
behaviors of these GUCs.

            regards, tom lane