David Rowley <dgrowle...@gmail.com> writes:
> I've not taken the time to fully understand this, but from reading the
> thread, I'm not immediately understanding why we can't just shallow
> copy the Path from the other RelOptInfo and replace the parent before
> using it in the upper RelOptInfo. Can you explain?
I did think about that, but "shallow copy a Path" seems nontrivial
because the Path structs are all different sizes. Maybe it is worth
building some infrastructure to support that?
regards, tom lane
