aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_target.c
diff options
context:
space:
mode:
authorRichard Guo <rguo@postgresql.org>2024-09-09 12:58:31 +0900
committerRichard Guo <rguo@postgresql.org>2024-09-09 12:58:31 +0900
commit87b6c3c0b703c3a71bc640f456a24937744ff30b (patch)
treeb4f3f4af3d93407eae7000e518dbbe9da8624b6a /src/backend/parser/parse_target.c
parentfc415edf8ca883b38cf8186f0d4b794d4a738cd5 (diff)
downloadpostgresql-87b6c3c0b703c3a71bc640f456a24937744ff30b.tar.gz
postgresql-87b6c3c0b703c3a71bc640f456a24937744ff30b.zip
Fix order of parameters in a cost_sort call
In label_sort_with_costsize, the cost_sort function is called with the parameters 'input_disabled_nodes' and 'input_cost' in the wrong order. This does not cause any plan diffs in the regression tests, because label_sort_with_costsize is only used to label the Sort node nicely for EXPLAIN, and cost numbers are not displayed in regression tests. Oversight in e22253467. Fixed by passing arguments in the right order. Per report from Alexander Lakhin running UBSan. Author: Alexander Lakhin Discussion: https://postgr.es/m/a9b7231d-68bc-f117-a07c-96688f3e6aef@gmail.com
Diffstat (limited to 'src/backend/parser/parse_target.c')
0 files changed, 0 insertions, 0 deletions