Re: Parallel INSERT (INTO ... SELECT ...)
От | Greg Nancarrow |
---|---|
Тема | Re: Parallel INSERT (INTO ... SELECT ...) |
Дата | |
Msg-id | CAJcOf-fd51zqtCOGCWa7=Gjx8Lh9nAApY6Q0rUq9hAfY1M4Msg@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: Parallel INSERT (INTO ... SELECT ...) ("Hou, Zhijie" <houzj.fnst@cn.fujitsu.com>) |
Список | pgsql-hackers |
On Mon, Feb 8, 2021 at 6:00 PM Hou, Zhijie <houzj.fnst@cn.fujitsu.com> wrote: > > > 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> > Thanks. You're right, I should probably update the docs to clarify those two cases. (I had removed them from the list of parallel-unsafe things, but not pointed out that a parallel table scan could still be used in these cases). Regards, Greg Nancarrow Fujitsu Australia
В списке pgsql-hackers по дате отправления: