[Bug] There is a problem with the distribution strategy of the orca unionall operator. #279
Open
2 tasks done
Labels
type: Bug
Something isn't working
Cloudberry Database version
master
What happened
The orca optimizer currently returns the ANY policy for the first child of a unionall-like node, which will result in Gather Motion for the downstream chi
ldren and a 1:n Redistribution for the upstream.
What you think should happen instead
remove child gather motion and upstream redis motion, just add 1:n to first child.
How to reproduce
tpcds 167 query
Operating System
centos7
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: