aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-12-16 20:14:25 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2019-12-16 20:14:35 -0500
commitb925a00f4ef65db9359e1c60fbf0e56d05afb25a (patch)
tree4050ae506297df680de96e15566084c8fb1ae8e4 /src/backend/tcop/postgres.c
parent9067b83955da5fde49a2605510900e6d9fa273af (diff)
downloadpostgresql-b925a00f4ef65db9359e1c60fbf0e56d05afb25a.tar.gz
postgresql-b925a00f4ef65db9359e1c60fbf0e56d05afb25a.zip
Fix "force_parallel_mode = regress" to work with ANALYZE + VERBOSE.
force_parallel_mode = regress is supposed to force use of a Gather node without having any impact on EXPLAIN output. But it failed to accomplish that if both ANALYZE and VERBOSE are given, because that enables per-worker output data that you wouldn't see if the Gather hadn't been inserted. Improve the logic so that we suppress the per-worker data too. This allows putting the new test case added by commit 5935917ce back into the originally intended form (cf. 776a2c887, 22864f6e0). We can also get rid of a kluge in subselect.sql, which previously had to clean up after force_parallel_mode's failure to do what it said on the tin. Discussion: https://postgr.es/m/18445.1576177309@sss.pgh.pa.us
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions