-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Query failure when FULL JOIN with not-equal predicate pushed down into PostgreSQL #14929
Comments
is this bug visible to Trino users? what's the example problematic query? |
In our test for FULL join with inequality operator for postgres
|
So it's actually a user visible bug. |
During work on Tests for different types of join, we noticed bug that some datasource (like postgres) not support some types of joins (like FULL OUTER) with some operators (inequality - <> < <= DISTINCT).
So we 'd like to disable some type of joins, based on conditions AND join types
#14841 (comment)
The text was updated successfully, but these errors were encountered: