| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zhenghua Lyu <zlyu(at)vmware(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: On disable_cost |
| Date: | 2024-04-03 20:03:44 |
| Message-ID: | CAKAnmmKkz4Oo_04UHk51u=R200XvOiuyKF=+Gx1H-o4577v9Tw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 3, 2024 at 3:21 PM Robert Haas <robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2024-04-03 20:04:26 | Re: Opportunistically pruning page before update |
| Previous Message | Tom Lane | 2024-04-03 20:02:47 | Re: Statistics Import and Export |