Backport to 2.15.x: #6917: Block OR BoolExpr from pushdown #6952
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
timescale-automation
added
the
is-auto-backport
fabriziomello
force-pushed
the
backport/2.15.x/6917
branch
2 times, most recently
from
a2bc419
to
4e7f47b
Compare
RestrictInfo with OR need special handling which we currently do not do which can lead to segfaults in planner if unhandled. (cherry picked from commit 01924c7)
fabriziomello
force-pushed
the
backport/2.15.x/6917
branch
from
4e7f47b
to
febd85f
Compare
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.
This is an automated backport of #6917: Block OR BoolExpr from pushdown.
The original issue is #6912.
This PR will be merged automatically after all the relevant CI checks pass. If this fix should not be backported, or will be backported manually, just close this PR. You can use the backport branch to add your changes, it won't be modified automatically anymore.
For more details, please see the documentation
Original description
Block OR BoolExpr from pushdown
RestrictInfo with OR need special handling which we currently do not do which can lead to segfaults in planner if unhandled.
Fixes#6912