Re: Parallel INSERT (INTO ... SELECT ...)
| От | Greg Nancarrow |
|---|---|
| Тема | Re: Parallel INSERT (INTO ... SELECT ...) |
| Дата | |
| Msg-id | CAJcOf-fqL++J6D16F5CV0wHLMj6rMtHY4h2wja6Sfrt4keJA2w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Parallel INSERT (INTO ... SELECT ...) (Amit Kapila <amit.kapila16@gmail.com>) |
| Ответы |
Re: Parallel INSERT (INTO ... SELECT ...)
|
| Список | pgsql-hackers |
> > What if this > > ends up being invoked from inside C code? > > > > I think it shouldn't be a problem unless one is trying to do something > like insert into foreign key table. So, probably we can have an Assert > to catch it if possible. Do you have any other idea? > Note that the planner code updated by the patch does avoid creating a Parallel INSERT plan in the case of inserting into a table with a foreign key (so commandIds won't be created in the parallel-worker code). I'm not sure how to distinguish the "invoked from inside C code" case though. Regards, Greg Nancarrow Fujitsu Australia
В списке pgsql-hackers по дате отправления: