On Fri, Mar 5, 2021 at 8:24 AM Greg Nancarrow <gregn4...@gmail.com> wrote: >
In patch v21-0003-Add-new-parallel-dml-GUC-and-table-options, we are introducing GUC (enable_parallel_dml) and table option (parallel_dml_enabled) for this feature. I am a bit worried about using *_dml in the names because it is quite possible that for parallel updates and parallel deletes we might not need any such GUC. The reason we mainly need here is due to checking of parallel-safety of partitioned tables and updates/deletes handle partitioned tables differently than inserts so those might not be that costly. It is possible that they are costly due to a different reason but not sure mapping those to one GUC or table option is a good idea. Can we consider using *_insert instead? I think GUC having _insert can be probably used for a parallel copy (from) as well which I think will have a similar overhead. -- With Regards, Amit Kapila.
