Re: Can we do something to help stop users mistakenly using force_parallel_mode? - Mailing list pgsql-hackers

From David Rowley
Subject Re: Can we do something to help stop users mistakenly using force_parallel_mode?
Date
Msg-id CAApHDvoyEiVTmpm74sbhaENJJpdYKxUDrpXTNj90NHp32vSi1Q@mail.gmail.com
Whole thread Raw
In response to Re: Can we do something to help stop users mistakenly using force_parallel_mode?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Can we do something to help stop users mistakenly using force_parallel_mode?
List pgsql-hackers
On Thu, 9 Feb 2023 at 11:26, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> David Rowley <dgrowleyml@gmail.com> writes:
> > I've attached a patch which does the renaming to debug_parallel_query.
> > I've made it so the old name can still be used.
>
> There's a better way to do that last, which is to add the translation to
> map_old_guc_names[].  I am not very sure what happens if you have multiple
> GUC entries pointing at the same underlying variable, but I bet that
> it isn't great.

Thanks for pointing that out. That might mean we can keep the
translation long-term as it won't appear in pg_settings and \dconfig,
or we might want to remove it if we want to be more deliberate about
breaking things for users who are misusing it. We maybe could just
consider that if/when all buildfarm animals are all using the new
name.

Attached updated patch.

David

Attachment

pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: Progress report of CREATE INDEX for nested partitioned tables
Next
From: Nathan Bossart
Date:
Subject: Re: Improve logging when using Huge Pages