aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2021-04-14 15:55:55 +0900
committerMichael Paquier <michael@paquier.xyz>2021-04-14 15:55:55 +0900
commitac725ee0f98c3fec703ffd9b070da629608e9a1e (patch)
treef476c1d71070d85a4aedef924e942cd33a0e52bb /src/backend/executor/nodeModifyTable.c
parent93f41461449f917da20af4fa2973f8afe8e6ea6e (diff)
downloadpostgresql-ac725ee0f98c3fec703ffd9b070da629608e9a1e.tar.gz
postgresql-ac725ee0f98c3fec703ffd9b070da629608e9a1e.zip
doc: Move force_parallel_mode to section for developer options
This GUC has always been classified as a planner option since its introduction in 7c944bd, and was listed in postgresql.conf.sample. As this parameter exists for testing purposes, move it to the section dedicated to developer parameters and hence remove it from postgresql.conf.sample. This will avoid any temptation to play with it on production servers for users that should never really have to touch this parameter. The general description used for developer options is reworded a bit, to take into account the inclusion of force_parallel_mode, per a suggestion from Tom Lane. Per discussion between Tom Lane, Bruce Momjian, Justin Pryzby, Bharath Rupireddy and me. Author: Justin Pryzby, Tom Lane Discussion: https://postgr.es/m/20210403152402.GA8049@momjian.us
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions