On Wed, Nov 1, 2017 at 6:20 PM, Jeevan Chalke <jeevan.chalke@enterprisedb.com> wrote: > Yep. > But as David reported earlier, if we remove the first part i.e. adding > cpu_operator_cost per tuple, Merge Append will be preferred over an Append > node unlike before. And thus, I thought of better having both, but no so > sure. Should we remove that part altogether, or add both in a single > statement with updated comments?
I was only suggesting that you update the comments.
OK. Done in the attached patch set.
I have rebased all my patches on latest HEAD which is at 7518049980be1d90264addab003476ae105f70d4
