Re: Rename EXISTS-to-ANY converted subplan to exists_to_any
От
solai v
Тема
Re: Rename EXISTS-to-ANY converted subplan to exists_to_any
Дата
Msg-id
CAF0whuefnuvSP5aaMBRf8Ca+hqk7DoAjr4tFpW_U17BaQQpjgw@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Rename EXISTS-to-ANY converted subplan to exists_to_any Yugo Nagata <nagata@sraoss.co.jp>
Re: Rename EXISTS-to-ANY converted subplan to exists_to_any Fujii Masao <masao.fujii@gmail.com>
Re: Rename EXISTS-to-ANY converted subplan to exists_to_any Fujii Masao <masao.fujii@gmail.com>
Hi, I tested this patch on the current HEAD. Before applying the patch, I observed that the converted subplan was displayed with the exists_ prefix in the EXPLAIN output. For example: Filter: ((ANY (a = (hashed SubPlan exists_2).col1)) OR (a < 0)) SubPlan exists_2 Even though the planner had internally converted the simple EXISTS subquery into an ANY subplan, the displayed name still used the exists_ prefix, which could be a little confusing when reading the execution plan. After applying the patch, the same query produced: Filter: ((ANY (a = (hashed SubPlan exists_to_any_1).col1)) OR (a < 0)) SubPlan exists_to_any_1 The new name makes it much clearer that this subplan is the result of an EXISTS-to-ANY conversion. I also verified that the query executed successfully before and after applying the patch. I didn't notice any change in the execution plan or query results ,the only visible difference was the improved subplan naming in the EXPLAIN output. Overall, the patch improves the readability of the user-visible plan without changing planner behavior. Regards, Solai
В списке pgsql-hackers по дате отправления
От: Daniel Gustafsson
Дата:
От: Fujii Masao
Дата: