aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/arrayfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-07-30 13:05:15 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2022-07-30 13:05:15 -0400
commitd8e34fa7a18fab4aa8eb010edac133d63ecc11c6 (patch)
treed9934332e1ff2c3e86df071f42131133432f8ca9 /src/backend/utils/adt/arrayfuncs.c
parentd10fad96c664a503a4203fc4b5acd4e816b0158a (diff)
downloadpostgresql-d8e34fa7a18fab4aa8eb010edac133d63ecc11c6.tar.gz
postgresql-d8e34fa7a18fab4aa8eb010edac133d63ecc11c6.zip
Fix incorrect is-this-the-topmost-join tests in parallel planning.
Two callers of generate_useful_gather_paths were testing the wrong thing when deciding whether to call that function: they checked for being at the top of the current join subproblem, rather than being at the actual top join. This'd result in failing to construct parallel paths for a sub-join for which they might be useful. While set_rel_pathlist() isn't actively broken, it seems best to make its identical-in-intention test for this be like the other two. This has been wrong all along, but given the lack of field complaints I'm hesitant to back-patch into stable branches; we usually prefer to avoid non-bug-fix changes in plan choices in minor releases. It seems not too late for v15 though. Richard Guo, reviewed by Antonin Houska and Tom Lane Discussion: https://postgr.es/m/CAMbWs4-mH8Zf87-w+3P2J=nJB+5OyicO28ia9q_9o=Lamf_VHg@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions