aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeHashjoin.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2005-11-20 18:38:20 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2005-11-20 18:38:20 +0000
commit40314f2dac2ecb2974d03c064917a70de74c63d5 (patch)
treeaa1f4d3aa30edf40a953dcc5e2b40bd342e96a8c /src/backend/executor/nodeHashjoin.c
parent33a9af738d24766ea487c56c2287102a9214c891 (diff)
downloadpostgresql-40314f2dac2ecb2974d03c064917a70de74c63d5.tar.gz
postgresql-40314f2dac2ecb2974d03c064917a70de74c63d5.zip
Modify tuptoaster's API so that it does not try to modify the passed
tuple in-place, but instead passes back an all-new tuple structure if any changes are needed. This is a much cleaner and more robust solution for the bug discovered by Alexey Beschiokov; accordingly, revert the quick hack I installed yesterday. With this change, HeapTupleData.t_datamcxt is no longer needed; will remove it in a separate commit in HEAD only.
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions