Re: Parallel sec scan in plpgsql

On Thu, Sep 22, 2016 at 7:32 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Sep 22, 2016 at 8:36 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> I think for certain cases like into clause, the rows passed will be
>> equal to actual number of rows, otherwise it will generate error. So
>> we can pass that information in executor layer. Another kind of cases
>> which are worth considering are when from plpgsql we fetch limited
>> rows at-a-time, but we fetch till end like the case of
>> exec_stmt_return_query().
>
> Yes, I think that those cases can be considered. Some careful code
> inspection will be needed to make sure the cases we want to enable are
> safe, and some testing will be needed to make sure they behave
> properly. But it doesn't sound like an unsolvable problem. I hope
> someone who isn't me will decide to work on it. :-)
>

makes sense. I think along with that we can also evaluate, if we can
enable parallel query from other pl languages. I think if we can
enable parallelism from all pl languages in 10.0, that will be a good
step forward.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com