| From: | "Hou, Zhijie" <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com> |
|---|---|
| To: | Greg Nancarrow <gregn4422(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, "David Rowley" <dgrowleyml(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)fujitsu(dot)com>, "Tang, Haiying" <tanghy(dot)fnst(at)cn(dot)fujitsu(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com> |
| Subject: | RE: Parallel INSERT (INTO ... SELECT ...) |
| Date: | 2021-02-08 06:59:56 |
| Message-ID: | 8f4ec40e02e1427ab584e9acdc4336b4@G08CNEXMBPEKD05.g08.fujitsu.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Posting an updated set of patches.
A minor comment about doc.
+ <para>
+ Where the above target table features are determined to be, at worst,
+ parallel-restricted, rather than parallel-unsafe, at least a parallel table
+ scan may be used in the query plan for the <literal>INSERT</literal>
+ statement. For more information about Parallel Safety, see
+ <xref linkend="parallel-safety"/>.
+ </para>
It seems does not mention that if target table is a foreign/temp table, a parallel table scan may be used.
So how about:
+ <para>
+ Where the target table is a foreign/temporary table or the above target table features
+ are determined to be, at worst, parallel-restricted, rather than parallel-unsafe,
+ at least a parallel table scan may be used in the query plan for the
+ <literal>INSERT</literal> statement. For more information about Parallel Safety,
+ see <xref linkend="parallel-safety"/>.
+ </para>
Best regards,
houzj
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Nancarrow | 2021-02-08 07:14:42 | Re: Parallel INSERT (INTO ... SELECT ...) |
| Previous Message | Greg Nancarrow | 2021-02-08 06:52:56 | Re: Parallel INSERT (INTO ... SELECT ...) |