Re: Converting SetOp to read its two inputs separately

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, David Rowley <dgrowleyml(at)gmail(dot)com>
Subject: Re: Converting SetOp to read its two inputs separately
Date: 2024-11-14 09:32:57
Message-ID: CAMbWs492vMy3XNjDZRtqtHfFTK6HVeDwhrEQH7eXGgF_h5Jnzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 14, 2024 at 6:28 PM Richard Guo <guofenglinux(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-11-14 09:46:05 Re: Virtual generated columns
Previous Message Richard Guo 2024-11-14 09:28:17 Re: Converting SetOp to read its two inputs separately