-
Notifications
You must be signed in to change notification settings - Fork 671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📘Fix missing ERROR: cannot push down this subquery
in set_operations
and subquery_in_where
#7741
Comments
39 tasks
colm-mchugh
changed the title
📘Fix missing
📘Fix missing Nov 13, 2024
ERROR: cannot push down this subquery
, could be the same issue as the above, seen in set_operations
ERROR: cannot push down this subquery
in set_operations
and subquery_in_where
colm-mchugh
added a commit
that referenced
this issue
Nov 14, 2024
Change the queries causing the test failures so that the ANY subquery cannot be folded to a join, preserving the expected output of the test.
This was referenced Nov 14, 2024
colm-mchugh
added a commit
that referenced
this issue
Nov 14, 2024
…in PG17 (#7741) Change the queries causing the test failures so that the ANY subquery cannot be folded to a join, preserving the expected output of the test.
colm-mchugh
added a commit
that referenced
this issue
Nov 15, 2024
…in PG17 (#7741) Change the queries causing the test failures so that the ANY subquery cannot be folded to a join, preserving the expected output of the test. Add pg17 regress test for pg17 features.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is the branch for the fix: https://github.com/citusdata/citus/tree/cmchugh/pg17-set_operations
The text was updated successfully, but these errors were encountered: