opt: fix panic with empty column sets in set operations #150706
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.
Fix panic "column statistics cannot be determined for empty column set" when performing set operations (UNION, INTERSECT, EXCEPT) on tables with no columns (e.g., created with "SELECT ALL").
Relatedly, relax the "invalid union" assertion in
CanConvertUnionToDistinctUnionAll that incorrectly assumed that we will never have an operation with no columns.
Fixes #130593
Release note: None
🤖 Generated with Claude Code