Re: [HACKERS] Enabling parallelism for queries coming from SQL orother PL functions
От | Dilip Kumar |
---|---|
Тема | Re: [HACKERS] Enabling parallelism for queries coming from SQL orother PL functions |
Дата | |
Msg-id | CAFiTN-tTjC3hLn8JjxP6w4Qwdp-vZNYApKyuBgQ5WKAFr2y6KA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Enabling parallelism for queries coming from SQL orother PL functions (Rafia Sabih <rafia.sabih@enterprisedb.com>) |
Ответы |
Re: [HACKERS] Enabling parallelism for queries coming from SQL orother PL functions
Re: [HACKERS] Enabling parallelism for queries coming from SQL orother PL functions |
Список | pgsql-hackers |
On Thu, Feb 23, 2017 at 12:11 PM, Rafia Sabih <rafia.sabih@enterprisedb.com> wrote: > Yes, it can be simplified to > if (dest->mydest == DestIntoRel || (numberTuples && (dest->mydest != > DestSPI && dest->mydest ! DestSQLFunction))) > Thanks. Okay, this looks cleaner. Few more comments. 1.I don't see any check in the code which will prevent the parallel execution of the query inside a function if its called from a DML statement. e.g. If we use a function in the update statement's which has the select statement. 2. How are you protecting, if the outer select is running in parallel, then the function called from there should not run anything in parallel? This may allow worker launching another set of workers. Am I missing something? -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: