aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/numeric.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-05-12 11:31:46 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2022-05-12 11:31:46 -0400
commit79b58c6f684315d39dfdbd721da7576d90bd9f99 (patch)
tree698fc3e6b6e09c83cd7d8a228019cc91fcfc4552 /src/backend/utils/adt/numeric.c
parent25285e5d4ee5b5655ddf93204180aedc873f19d6 (diff)
downloadpostgresql-79b58c6f684315d39dfdbd721da7576d90bd9f99.tar.gz
postgresql-79b58c6f684315d39dfdbd721da7576d90bd9f99.zip
Make pull_var_clause() handle GroupingFuncs exactly like Aggrefs.
This follows in the footsteps of commit 2591ee8ec by removing one more ill-advised shortcut from planning of GroupingFuncs. It's true that we don't intend to execute the argument expression(s) at runtime, but we still have to process any Vars appearing within them, or we risk failure at setrefs.c time (or more fundamentally, in EXPLAIN trying to print such an expression). Vars in upper plan nodes have to have referents in the next plan level, whether we ever execute 'em or not. Per bug #17479 from Michael J. Sullivan. Back-patch to all supported branches. Richard Guo Discussion: https://postgr.es/m/17479-6260deceaf0ad304@postgresql.org
Diffstat (limited to 'src/backend/utils/adt/numeric.c')
0 files changed, 0 insertions, 0 deletions