| From: | "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com> |
|---|---|
| To: | Greg Nancarrow <gregn4422(at)gmail(dot)com> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Tsunakawa, Takayuki/綱川 貴之 <tsunakawa(dot)takay(at)fujitsu(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Subject: | RE: Parallel INSERT SELECT take 2 |
| Date: | 2021-08-05 09:41:10 |
| Message-ID: | OS3PR01MB5718E56D9ABCEABF08B44F3D94F29@OS3PR01MB5718.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Based on the discussion in another thread[1], we plan to change the design like
the following:
allow users to specify a parallel-safety option for both partitioned and
non-partitioned relations but for non-partitioned relations if users didn't
specify, it would be computed automatically? If the user has specified
parallel-safety option for non-partitioned relation then we would consider that
instead of computing the value by ourselves.
In this approach, it will be more convenient for users to use and get the
benefit of parallel select for insert.
Since most of the technical discussion happened in another thread, I
posted the new version patch including the new design to that thread[2].
Comments are also welcome in that thread.
Best regards,
houzj
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Guo | 2021-08-05 10:18:03 | Re: Two patches to speed up pg_rewind. |
| Previous Message | Michael Banck | 2021-08-05 09:27:28 | Re: Commitfest overflow |