| From: | "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Zhihong Yu <zyu(at)yugabyte(dot)com>, Luc Vlaming <luc(at)swarm64(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
| Subject: | RE: Parallel Inserts in CREATE TABLE AS |
| Date: | 2021-03-19 09:05:13 |
| Message-ID: | OS0PR01MB571617D127B5C4EABBE3784F94689@OS0PR01MB5716.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> They are pretty simple though. I think someone can also check if the same
> regression exists for parallel inserts in "INSERT INTO SELECT"
> patch set as well for larger tuple sizes.
Thanks for reminding.
I did some performance tests for parallel inserts in " INSERT INTO SELECT " with the testcase you provided,
the regression seems does not exists in "INSERT INTO SELECT".
I will try to test with larger tuple size later.
Best regards,
houzj
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yugo NAGATA | 2021-03-19 09:17:26 | Re: Columns correlation and adaptive query optimization |
| Previous Message | Marina Polyakova | 2021-03-19 08:32:53 | Re: Reduce the time required for a database recovery from archive. |