On Fri, Dec 18, 2020 at 10:08 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
> I think it will be clean to implement the parallel CTAS when a
> top-level node is the gather node. Basically, the idea is that
> whenever we get the gather on the top which doesn't have any
> projection then we can push down the dest receiver directly to the
> worker. I agree that append is an exception that doesn't do any extra
> processing other than appending the results, So IMHO it would be
> better that in the first part we parallelize the plan where gather
> node on top. I see that we have already worked on the patch where the
> append node is on top so I would suggest that we can keep that part in
> a separate patch.
Thanks! I rearranged the patches to keep the append part separate in
the 0004 patch.
Attaching v13 patch set:
0001 - parallel inserts in ctas without planner enforcement for tuple
cost calculation
0002 - planner enforcement for tuple cost calculation
0003 - tests
0004 - enabling parallel inserts for Append cases, related planner
enforcement code and tests.
Please consider these patches for further review.
With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com