Re: [HACKERS] COPY (query) TO ... doesn't allow parallelism
| От | Amit Kapila |
|---|---|
| Тема | Re: [HACKERS] COPY (query) TO ... doesn't allow parallelism |
| Дата | |
| Msg-id | CAA4eK1J1j_z2Aw3OpVigv9EScJvxAnYOrkV5=T4Dph_==sYjew@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] COPY (query) TO ... doesn't allow parallelism (Andres Freund <andres@anarazel.de>) |
| Ответы |
Re: [HACKERS] COPY (query) TO ... doesn't allow parallelism
|
| Список | pgsql-hackers |
On Thu, Jun 1, 2017 at 9:34 PM, Andres Freund <andres@anarazel.de> wrote: > On 2017-06-01 21:23:04 +0530, Amit Kapila wrote: >> On a related note, I think it might be better to have an >> IsInParallelMode() check in this case as we have at other places. >> This is to ensure that if this command is invoked via plpgsql function >> and that function runs is the parallel mode, it will act as a >> safeguard. > > Hm? Which other places do it that way? Isn't standard_planner() > centralizing such a check? > heap_insert->heap_prepare_insert, heap_update, heap_delete, etc. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: