| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Zhenghua Lyu <zlv(at)pivotal(dot)io>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: On disable_cost |
| Date: | 2019-11-01 16:22:06 |
| Message-ID: | CA+Tgmob4+Eu5LN4j1XEMQDtCFFLKuUCEJebND3bWrQL0-N7VTA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 1, 2019 at 12:00 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> That seems like a bad idea - we add the cost multiple times. And we
> still want to compare plans that potentially involve that cost, if
> there's no other way to plan the query.
Yeah. I kind of wonder if we shouldn't instead (a) skip adding paths
that use methods which are disabled and then (b) if we don't end up
with any paths for that reloptinfo, try again, ignoring disabling
GUCs.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilles Darold | 2019-11-01 16:29:23 | [PATCH][DOC] Fix for PREPARE TRANSACTION doc and postgres_fdw message. |
| Previous Message | Konstantin Knizhnik | 2019-11-01 16:09:49 | Re: [Proposal] Global temporary tables |