| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Thom Brown <thom(at)linux(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: assessing parallel-safety |
| Date: | 2015-07-16 03:37:06 |
| Message-ID: | CAA4eK1Lo2K_0HzYhsc92ULHwYJMY1c+qa-c1pN04KOOtWfnaVA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 16, 2015 at 2:02 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> exec_stmt_execsql is called by exec_stmt_open and exec_stmt_forc.
> Those are cursor operations and thus - I think - parallelism can't be
> used there.
Right, but it also gets called from exec_stmt where a parallel-safe
statement could be passed to it. So it seems to me that we
should enable parallelism for that path in code.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-07-16 03:43:46 | Re: [PATCH] postgres_fdw extension support |
| Previous Message | Amit Kapila | 2015-07-16 03:10:46 | Re: Parallel Seq Scan |