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

On Wed, 12 Apr 2023 at 09:53, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I don't see a reason to wait longer once the buildfarm is on board.

I did a final sweep of the latest runs for each animal this morning.
Everything has been switched over to debug_parallel_query, so I've
gone and pushed the patch to remove the mapping.

For the record, the only things I see mentioning force_parallel_mode
in there are:

hoverfly
<td>force_parallel_mode; RANDOMIZE_ALLOCATED_MEMORY</td>
mantid
<td>force_parallel_mode on REL_10_STABLE and later</td>

'force_parallel_mode = regress'

'force_parallel_mode = regress'

'force_parallel_mode = regress'

'force_parallel_mode = regress'

'force_parallel_mode = regress'
mandrill
<td>force_parallel_mode; RANDOMIZE_ALLOCATED_MEMORY</td>
seawasp
<a href="https://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=98a88bc2bc">98a88bc2bc</a>
Thu Mar 2 22:47:20 2023 UTC Harden new test case against
force_parallel_mode = regress.
<a href="https://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5352ca22e0">5352ca22e0</a>
Wed Feb 15 08:21:59 2023 UTC Rename force_parallel_mode to
debug_parallel_query

seawasp's is just references to older commits. The rest seem like
just outdated comments.

David