On Thu, Mar 23, 2017 at 5:23 AM, Dilip Kumar <dilipbal...@gmail.com> wrote: > On Wed, Mar 22, 2017 at 10:33 PM, Robert Haas <robertmh...@gmail.com> wrote: >> So couldn't we actually make this test !fcache->returnsSet || !es->lazyEval? >> That would let us allow parallel execution for all non-set-returning >> functions, and also for set-returning functions that end up with >> es->lazyEval set to false. > > Yes, this is the right thing to do although we may not enable > parallelism for any more queries by adding "|| !es->lazyEval". Because > SELECT are always marked as es->lazyEval=true(And so far we have > parallelism only for select). But here we calling the parameter to > ExecutorRun as execute_once so !fcache->returnsSet || !es->lazyEval > is the correct one and future proof. > Agree, done.
-- Regards, Rafia Sabih EnterpriseDB: http://www.enterprisedb.com/
execute-once-v3.patch
Description: Binary data
pl_parallel_opt_support_v3.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
