aboutsummaryrefslogtreecommitdiff
path: root/src/backend/jit/llvm/llvmjit_expr.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-11-30 14:38:00 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2020-11-30 14:38:00 -0500
commitfac31b2cd4470124d7d68a7eebdb13cfff8b3d3d (patch)
tree20db95a44c89570174ea02cd078b2b79228df6ed /src/backend/jit/llvm/llvmjit_expr.c
parent666a4de939bf78df7295c35899a5f2e89eaea382 (diff)
downloadpostgresql-fac31b2cd4470124d7d68a7eebdb13cfff8b3d3d.tar.gz
postgresql-fac31b2cd4470124d7d68a7eebdb13cfff8b3d3d.zip
Prevent parallel index build in a standalone backend.
This can't work if there's no postmaster, and indeed the code got an assertion failure trying. There should be a check on IsUnderPostmaster gating the use of parallelism, as the planner has for ordinary parallel queries. Commit 40d964ec9 got this right, so follow its model of checking IsUnderPostmaster at the same place where we check for max_parallel_maintenance_workers == 0. In general, new code implementing parallel utility operations should do the same. Report and patch by Yulin Pei, cosmetically adjusted by me. Back-patch to v11 where this code came in. Discussion: https://postgr.es/m/HK0PR01MB22747D839F77142D7E76A45DF4F50@HK0PR01MB2274.apcprd01.prod.exchangelabs.com
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_expr.c')
0 files changed, 0 insertions, 0 deletions