Re: assessing parallel-safety - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: assessing parallel-safety
Date
Msg-id CAA4eK1Lo2K_0HzYhsc92ULHwYJMY1c+qa-c1pN04KOOtWfnaVA@mail.gmail.com
Whole thread Raw
In response to Re: assessing parallel-safety  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, Jul 16, 2015 at 2:02 AM, Robert Haas <robertmhaas@gmail.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

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Parallel Seq Scan
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] postgres_fdw extension support