Re: Converting SetOp to read its two inputs separately - Mailing list pgsql-hackers

From Richard Guo
Subject Re: Converting SetOp to read its two inputs separately
Date
Msg-id CAMbWs492vMy3XNjDZRtqtHfFTK6HVeDwhrEQH7eXGgF_h5Jnzw@mail.gmail.com
Whole thread Raw
In response to Re: Converting SetOp to read its two inputs separately  (Richard Guo <guofenglinux@gmail.com>)
Responses Re: Converting SetOp to read its two inputs separately
List 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 by date:

Previous
From: Richard Guo
Date:
Subject: Re: Converting SetOp to read its two inputs separately
Next
From: Amit Kapila
Date:
Subject: Re: Virtual generated columns