Re: On disable_cost
От | Laurenz Albe |
---|---|
Тема | Re: On disable_cost |
Дата | |
Msg-id | 7f6f41796b8d110dc1ef6e7898ea35eab9345144.camel@cybertec.at обсуждение исходный текст |
Ответ на | Re: On disable_cost (Alena Rybakina <a.rybakina@postgrespro.ru>) |
Ответы |
Re: On disable_cost
|
Список | pgsql-hackers |
On Wed, 2024-10-02 at 21:31 +0300, Alena Rybakina wrote: > Honestly, I like this patch. Before this patch, when disabling any algorithm > in the optimizer, the cost increased significantly and I’m not sure that this > was a reliable solution due to the fact that the cost even without disabling > can be greatly increased because of the high cardinality, for example. > > Right there, the mechanism is simple and more honest in my opinion - we simply > count the number of disabled nodes and discard the paths with the largest > number of them. I have no issue with this way of handling disabled plan nodes, I only complained about the verbosity of the EXPLAIN output. I don't want to see disabled nodes propagated all the way up the tree, and I would like the output suppressed by default. Yours, Laurenz Albe
В списке pgsql-hackers по дате отправления: