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.
Fuzzer issue #5984 no. 16
Problem query:
My findings:
The JOIN condition is split into filter expressions ( c0 <= c1 ) and (c1 <= 1) and after that,
an additional transitive filter is created to compare c0 with 1.
However the expression (c1 <= 1) seems to have cast the constant’s logical type to USMALLINT in a previous optimizer step, probably because it’s more efficient than casting the entire c1 column.
But this in turn causes a problem when comparing c0 with 1 (INT <= USMALLINT)
My current solution is to only create transitive filters when the logical types match.
This does not solve the second problem query from the fuzzer issue though, so that part still needs fixing :(