Re: Parallel sec scan in plpgsql - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Parallel sec scan in plpgsql
Date
Msg-id CAA4eK1LzNPdYxQsG6bBXjZ=8rX2c8XyUKQy+OA+QaZ9_AV0+Sw@mail.gmail.com
Whole thread Raw
In response to Re: Parallel sec scan in plpgsql  (Alex Ignatov <a.ignatov@postgrespro.ru>)
Responses Re: Parallel sec scan in plpgsql  (Alex Ignatov <a.ignatov@postgrespro.ru>)
List pgsql-hackers
On Fri, Sep 16, 2016 at 6:57 PM, Alex Ignatov <a.ignatov@postgrespro.ru> wrote:
> No it doesn't.
> Paralleling neither sql function nor plpgsql:
> Here is example :
>
> ipdr=> show max_worker_processes ;
>  max_worker_processes
> ----------------------
>  128
> (1 row)
> ipdr=> set max_parallel_workers_per_gather to 128;
> SET
> ipdr=> set force_parallel_mode=on;
> SET
> ipdr=> set min_parallel_relation_size =0;
> SET
> ipdr=> set parallel_tuple_cost=0;
> SET
>

Can you try by setting force_parallel_mode = off;?  I think it is
sending the whole function execution to worker due to
force_parallel_mode.


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



pgsql-hackers by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: Vacuum: allow usage of more than 1GB of work mem
Next
From: Jeevan Chalke
Date:
Subject: Re: Aggregate Push Down - Performing aggregation on foreign server