Re: Can we do something to help stop users mistakenly using force_parallel_mode?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: David Rowley <dgrowleyml(at)gmail(dot)com>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: Can we do something to help stop users mistakenly using force_parallel_mode?
Date: 2023-02-10 15:33:55
Message-ID: 374c5d0a-d651-6a26-3871-1f542dc9aa30@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2023-02-09 Th 15:25, David Rowley wrote:
> On Thu, 9 Feb 2023 at 21:20, John Naylor<john(dot)naylor(at)enterprisedb(dot)com> wrote:
>> Looks good at a glance, just found a spurious word:
>>
>> + "by forcing the planner into to generate plans which contains nodes "
> Thanks for looking. I'll fix that.
>
> Likely the hardest part to get right here is the new name. Can anyone
> think of anything better than debug_parallel_query?
>

WFM

cheers

andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Drouvot, Bertrand 2023-02-10 15:50:32 Re: Reconcile stats in find_tabstat_entry() and get rid of PgStat_BackendFunctionEntry
Previous Message Andrew Dunstan 2023-02-10 15:21:49 Re: run pgindent on a regular basis / scripted manner