Add comparison keys to plan string for in-union #2900
Draft
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
comparisonKeyFunction
is currently not included in the plan representation ofInUnion
plans. This can make it hard to inspect bugs that could be a result of an in-union improperly merging results from different legs of a union. This does make the plan representation a little more verbose, though hopefully manageably so. It should be less intrusive, for example, than a regular union, which puts the comparison key between each leg of the union (unless the comparison is by primary key).