Dept of second thoughts: after studying index_getnext() a bit more I realize
Tom Lane <tgl@sss.pgh.pa.us>
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.
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/access/hash/hash.c | modified | +8 −3 |
| src/backend/access/hash/hashsearch.c | modified | +3 −3 |
| src/include/access/hash.h | modified | +5 −2 |