Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Tom Lane wrote:
>> Actually ... if you intend to allow column storage to work with inherited
>> tables (and if you don't, you'd better have a darn good reason why not),
>> I think you probably want to do this join insertion *after* inheritance
>> expansion, so you can join child column stores only to the appropriate
>> child heap table, and not to the entire inheritance tree.
> Won't this cause issues to MergeAppend optimizations?
Like what? And if there are such issues, why do you think you wouldn't
be expected to solve them?
regards, tom lane
