ReflectedXss: Prevent bad join order#12333
Merged
Merged
Conversation
5d38650 to
d1bd850
Compare
d1bd850 to
8692564
Compare
erik-krogh
approved these changes
Mar 1, 2023
Contributor
erik-krogh
left a comment
There was a problem hiding this comment.
Looks very reasonable.
And I assume you've benchmarked that it doesn't cause a regression with the current join-orderer.
Contributor
Author
|
Yes, see the referenced DCA experiment. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The Core team is planning to make some changes to the join orderer that causes a join order regression for the
isLocalHeaderDefinitionpredicate. This PR adds pragmas to prevent the compiler from picking the bad join order.