Re: Converting SetOp to read its two inputs separately
От | Richard Guo |
---|---|
Тема | Re: Converting SetOp to read its two inputs separately |
Дата | |
Msg-id | CAMbWs492vMy3XNjDZRtqtHfFTK6HVeDwhrEQH7eXGgF_h5Jnzw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Converting SetOp to read its two inputs separately (Richard Guo <guofenglinux@gmail.com>) |
Ответы |
Re: Converting SetOp to read its two inputs separately
|
Список | pgsql-hackers |
On Thu, Nov 14, 2024 at 6:28 PM Richard Guo <guofenglinux@gmail.com> wrote: > 1. We need to teach set_operation_ordered_results_useful() that sorted > input paths are also useful for INTERSECT/EXCEPT, so that we can have > setop_pathkeys set for the subqueries. BTW, I noticed a typo in the comment for function set_operation_ordered_results_useful(). * set_operation_ordered_results_useful * Return true if the given SetOperationStmt can be executed by utilizing * paths that provide sorted input according to the setop's targetlist. - * Returns false when sorted paths are not any more useful then unsorted + * Returns false when sorted paths are not any more useful than unsorted * ones. Thanks Richard
В списке pgsql-hackers по дате отправления: