aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-11-01 22:31:02 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-11-01 22:31:02 +0000
commit01adc8afd55f3ae831e32b6ce19f7c61f4baac28 (patch)
treeec4ba5825187ce28c6aaae7a8a1aa64fbd44ceae /src/backend/access/gist
parent891e225a7066e1922cfcf023a4aff2e1444d020b (diff)
downloadpostgresql-01adc8afd55f3ae831e32b6ce19f7c61f4baac28.tar.gz
postgresql-01adc8afd55f3ae831e32b6ce19f7c61f4baac28.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/access/gist')
0 files changed, 0 insertions, 0 deletions