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>
Cc: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, 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-15 01:10:01
Message-ID: 5431a2ef-ec2f-b0c6-0021-9e8297b31d61@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2023-02-14 Tu 17:32, David Rowley wrote:
> On Wed, 15 Feb 2023 at 11:27, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>> It's just occurred to me that this could break the buildfarm fairly comprehensively. I just took a count and we have 74 members using force_parallel_mode. Maybe we need to keep force_parallel_mode as an alternative spelling for debug_parallel_query until we can get them all switched over. I know it's more trouble ...
> Yeah, I mentioned in [1] about that and took measures there to keep
> the old name in place. In the latest patch, there's an entry in
> map_old_guc_names[] to allow the old name to work. I think the
> buildfarm will still work ok because of that.

Oops, I missed or forgot that.

>
> What I'm not so sure about is how to go about getting all owners to
> change the config for versions >= PG16. Is that a question of emailing
> each owner individually to ask them if they can make the change? Or
> should we just forever keep the map_old_guc_names[] entry for this?

We'll email them once this is in. Most people are fairly reponsive.

cheers

andrew

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2023-02-15 01:14:54 Re: make_ctags: use -I option to ignore pg_node_attr macro
Previous Message Peter Smith 2023-02-15 01:09:13 Re: [PATCH] Add pretty-printed XML output option