Re: On disable_cost - Mailing list pgsql-hackers

From Robert Haas
Subject Re: On disable_cost
Date
Msg-id CA+Tgmob4+Eu5LN4j1XEMQDtCFFLKuUCEJebND3bWrQL0-N7VTA@mail.gmail.com
Whole thread Raw
In response to Re: On disable_cost  (Andres Freund <andres@anarazel.de>)
Responses Re: On disable_cost  (Jim Finnerty <jfinnert@amazon.com>)
Re: On disable_cost  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Fri, Nov 1, 2019 at 12:00 PM Andres Freund <andres@anarazel.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



pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: [Proposal] Global temporary tables
Next
From: Gilles Darold
Date:
Subject: [PATCH][DOC] Fix for PREPARE TRANSACTION doc and postgres_fdwmessage.