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 CAApHDvoDZCb=xhWZ-obsMRQWqpjBgJDe5RC=cvCNdG9M+vZj-Q@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>)
List pgsql-hackers
On Wed, 12 Apr 2023 at 09:53, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> David Rowley <dgrowleyml@gmail.com> writes:
> > In preparation for when that's ticked off, I'd like to gather people's
> > thoughts about if we should remove force_parallel_mode from v16?
>
> To clarify, you just mean removing that alias, right?  +1.
> I don't see a reason to wait longer once the buildfarm is on board.

Yip, alias. i.e:

diff --git a/src/backend/utils/misc/guc.c b/src/backend/utils/misc/guc.c
index ea67cfa5e5..7d3b20168a 100644
--- a/src/backend/utils/misc/guc.c
+++ b/src/backend/utils/misc/guc.c
@@ -186,7 +186,6 @@ static const unit_conversion time_unit_conversion_table[] =
 static const char *const map_old_guc_names[] = {
        "sort_mem", "work_mem",
        "vacuum_mem", "maintenance_work_mem",
-       "force_parallel_mode", "debug_parallel_query",
        NULL
 };

David



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: ERROR messages in VACUUM's PARALLEL option
Next
From: Andres Freund
Date:
Subject: Re: Assertion being hit during WAL replay