aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/execParallel.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2018-11-06 14:11:21 +0900
committerMichael Paquier <michael@paquier.xyz>2018-11-06 14:11:21 +0900
commit8f045e242b2308473f5de532590454294e3d5683 (patch)
tree89837935be9ab9cbf3445d4874b47d10cd54ba84 /src/backend/executor/execParallel.c
parent3c60d0fa231f7699af5dd83345919d0423305973 (diff)
downloadpostgresql-8f045e242b2308473f5de532590454294e3d5683.tar.gz
postgresql-8f045e242b2308473f5de532590454294e3d5683.zip
Switch pg_promote to be parallel-safe
pg_promote uses nothing relying on a global state, so it is fine to mark it as parallel-safe, conclusion based on a detailed analysis from Robert Haas. This also fixes an inconsistency where pg_proc.dat missed to mark the function with its previous value for proparallel, update which does not matter now as the default is used. Based on a discussion between multiple folks: Laurenz Albe, Robert Haas, Amit Kapila, Tom Lane and myself. Discussion: https://postgr.es/m/20181029082530.GL14242@paquier.xyz
Diffstat (limited to 'src/backend/executor/execParallel.c')
0 files changed, 0 insertions, 0 deletions