Re: crashes due to setting max_parallel_workers=0 - Mailing list pgsql-hackers

From David Rowley
Subject Re: crashes due to setting max_parallel_workers=0
Date
Msg-id CAKJS1f_-c9ZwepOMJF+P9HL_7V_4LKtV0htFjJgO7JjEVAf2nA@mail.gmail.com
Whole thread Raw
In response to Re: crashes due to setting max_parallel_workers=0  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
On 27 March 2017 at 10:23, Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote:
> I'm not sure we need to invent a new magic value, though. Can we simply look
> at force_parallel_mode, and if it's 'regress' then tread 0 differently?

see standard_planner()

if (force_parallel_mode != FORCE_PARALLEL_OFF && best_path->parallel_safe)
{
Gather   *gather = makeNode(Gather);


Probably force_parallel_mode is good for testing the tuple queue code,
and some code in Gather, but I'm not quite sure what else its good
for. Certainly not GatherMerge.



-- David Rowley                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Venkata B Nagothi
Date:
Subject: Re: patch proposal
Next
From: Michael Paquier
Date:
Subject: Re: Speedup twophase transactions