Re: Parallel execution and prepared statements
От | Robert Haas |
---|---|
Тема | Re: Parallel execution and prepared statements |
Дата | |
Msg-id | CA+TgmoZGLZ+HT8gA=7L9UkwwnGSf4Sor8o990we58H+hYj+qrQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Parallel execution and prepared statements (Tobias Bussmann <t.bussmann@gmx.net>) |
Ответы |
Re: Parallel execution and prepared statements
|
Список | pgsql-hackers |
On Tue, Nov 15, 2016 at 3:57 PM, Tobias Bussmann <t.bussmann@gmx.net> wrote: > As the patch in [1] targeting the execution of the plan in ExecutePlan depending on the destination was declined, I hackedaround a bit to find another way to use parallel mode with SQL prepared statements while disabling the parallel executionin case of an non read-only execution. For this I used the already present test for an existing intoClause in ExecuteQueryto set the parallelModeNeeded flag of the prepared statement. This results in a non parallel execution of theparallel plan, as we see with a non-zero fetch count used with the extended query protocol. Despite this patch seem towork in my tests, I'm by no means confident this being a proper way of handling the situation in question. Yeah, we could do something like this, perhaps not in exactly this way, but I'm not sure it's a good idea to just execute the parallel plan without workers. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: