Cherry-pick from Greenplum: [ORCA] Avoid pushdown of predicate with set-returning function (#14201) #715
+958
−71
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Issue is that if a predicate with a set-returning function is pushed down then it can lead to bad execution because there exist cases where the below context cannot accept a set. Logic already existed to prevent such a case, but it wasn't sufficient. Following example demonstrates such a case: ```sql CREATE TABLE t(a int[]) ; INSERT INTO t VALUES (ARRAY[1, 2]); SELECT * FROM (SELECT unnest(t1.a) a_unnest FROM t t1, t t2) s WHERE a_unnest IS NOT NULL; ``` Also similarly, do not push down a filter through a projected column containing a subquery.
jiaqizho
approved these changes
Nov 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick ORCA commits from GreenPlum