| From: | "Hou, Zhijie" <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com> |
|---|---|
| To: | vignesh C <vignesh21(at)gmail(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Subject: | RE: Parallel copy |
| Date: | 2020-12-23 09:35:25 |
| Message-ID: | c2ce59030aab43edadcd0c8aae516220@G08CNEXMBPEKD05.g08.fujitsu.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
> Yes this optimization can be done, I will handle this in the next patch
> set.
>
I have a suggestion for the parallel safety-check.
As designed, The leader does not participate in the insertion of data.
If User use (PARALLEL 1), there is only one worker process which will do the insertion.
IMO, we can skip some of the safety-check in this case, becase the safety-check is to limit parallel insert.
(except temporary table or ...)
So, how about checking (PARALLEL 1) separately ?
Although it looks a bit complicated, But (PARALLEL 1) do have a good performance improvement.
Best regards,
houzj
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ajin Cherian | 2020-12-23 09:38:38 | Re: [HACKERS] logical decoding of two-phase transactions |
| Previous Message | Andrey V. Lepikhov | 2020-12-23 09:00:18 | Re: [POC] Fast COPY FROM command for the table with foreign partitions |