Re: Enabling parallelism for queries coming from SQL or other PL functions

On Thu, Feb 23, 2017 at 9:20 PM, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> On Thu, Feb 23, 2017 at 8:58 PM, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>> 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.
>
> Having said that, I am thinking do we really need to block such cases?
> It just looks fine to me that an update statement calls a function (in
> targetlist or condition), which launches a bunch of workers for the
> internal query inside PL; finishes the work and shutdown them, only
> after this, the update will change any record. So basically I want to
> make a point that between the worker launch and shutdown there is no
> change in the database state.
>

+1. I also think you are right that there should not be a problem in
such a case.

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