aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-11-01 22:30:54 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-11-01 22:30:54 +0000
commit7d535ebe5bf95ca88891c0288fa1c6575498185e (patch)
tree3b26f8d66fde2c0c192c3df03691b0ff28c5a747 /src/backend/executor/nodeFunctionscan.c
parentc4afdca4c26df63e4942ef300e544c7118c6af56 (diff)
downloadpostgresql-7d535ebe5bf95ca88891c0288fa1c6575498185e.tar.gz
postgresql-7d535ebe5bf95ca88891c0288fa1c6575498185e.zip
Dept of second thoughts: after studying index_getnext() a bit more I realize
that it can scribble on scan->xs_ctup.t_self while following HOT chains, so we can't rely on that to stay valid between hashgettuple() calls. Introduce a private variable in HashScanOpaque, instead.
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions