Re: On disable_cost

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: On disable_cost
Дата
Msg-id CA+Tgmob4+Eu5LN4j1XEMQDtCFFLKuUCEJebND3bWrQL0-N7VTA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: On disable_cost  (Andres Freund <andres@anarazel.de>)
Ответы Re: On disable_cost  (Jim Finnerty <jfinnert@amazon.com>)
Re: On disable_cost  (Andres Freund <andres@anarazel.de>)
Список 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 по дате отправления:

Предыдущее
От: Konstantin Knizhnik
Дата:
Сообщение: Re: [Proposal] Global temporary tables
Следующее
От: Gilles Darold
Дата:
Сообщение: [PATCH][DOC] Fix for PREPARE TRANSACTION doc and postgres_fdwmessage.