Re: On disable_cost - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: On disable_cost
Date
Msg-id CAKAnmmKkz4Oo_04UHk51u=R200XvOiuyKF=+Gx1H-o4577v9Tw@mail.gmail.com
Whole thread Raw
In response to Re: On disable_cost  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Apr 3, 2024 at 3:21 PM Robert Haas <robertmhaas@gmail.com> wrote: 
It's also pretty clear to me that the fact that enable_indexscan
and enable_indexonlyscan work completely differently from each other
is surprising at best, wrong at worst, but here again, what this patch
does about that is not above reproach.

Yes, that is wrong, surely there is a reason we have two vars. Thanks for digging into this: if nothing else, the code will be better for this discussion, even if we do nothing for now with disable_cost.

Cheers,
Greg


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Statistics Import and Export
Next
From: Melanie Plageman
Date:
Subject: Re: Opportunistically pruning page before update