aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/execProcnode.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-01-11 15:31:12 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-01-11 15:31:12 +0000
commitbfa084fb0de2ba7ded493ba27ea280a6ec0e69bd (patch)
tree6759605ab315479ae55efc89658ae9cf441a10fe /src/backend/executor/execProcnode.c
parent48eb3e635162d8a53034010d32382dc5aaf2cfdc (diff)
downloadpostgresql-bfa084fb0de2ba7ded493ba27ea280a6ec0e69bd.tar.gz
postgresql-bfa084fb0de2ba7ded493ba27ea280a6ec0e69bd.zip
Improve ExecEvalVar's handling of whole-row variables in cases where the
rowtype contains dropped columns. Sometimes the input tuple will be formed from a select targetlist in which dropped columns are filled with a NULL of an arbitrary type (the planner typically uses INT4, since it can't tell what type the dropped column really was). So we need to relax the rowtype compatibility check to not insist on physical compatibility if the actual column value is NULL. In principle we might need to do this for functions returning composite types, too (see tupledesc_match()). In practice there doesn't seem to be a bug there, probably because the function will be using the same cached rowtype descriptor as the caller. Fixing that code path would require significant rearrangement, so I left it alone for now. Per complaint from Filip Rembialkowski.
Diffstat (limited to 'src/backend/executor/execProcnode.c')
0 files changed, 0 insertions, 0 deletions