Dept of second thoughts: after studying index_getnext() a bit more I realize
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 1 Nov 2009 22:30:54 +0000 (22:30 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 1 Nov 2009 22:30:54 +0000 (22:30 +0000)
commit7d535ebe5bf95ca88891c0288fa1c6575498185e
tree3b26f8d66fde2c0c192c3df03691b0ff28c5a747
parentc4afdca4c26df63e4942ef300e544c7118c6af56
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.
src/backend/access/hash/hash.c
src/backend/access/hash/hashsearch.c
src/include/access/hash.h