aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2019-04-19 11:25:48 -0700
committerAndres Freund <andres@anarazel.de>2019-04-19 11:42:37 -0700
commitb8b94ea129ffc988c2d30eb2b5aa65a93329b8fa (patch)
tree11eb2a539adeeb5cfdc2af59a94ad7fd4a26940a /src/backend/access/gist/gist.c
parent88e6ad3054ddd5aa0dee12e5def2c335fe92a414 (diff)
downloadpostgresql-b8b94ea129ffc988c2d30eb2b5aa65a93329b8fa.tar.gz
postgresql-b8b94ea129ffc988c2d30eb2b5aa65a93329b8fa.zip
Fix slot type issue for fuzzy distance index scan over out-of-core table AM.
For amcanreorderby scans the nodeIndexscan.c's reorder queue holds heap tuples, but the underlying table likely does not. Before this fix we'd return different types of slots, depending on whether the tuple came from the reorder queue, or from the index + table. While that could be fixed by signalling that the node doesn't return a fixed type of slot, it seems better to instead remove the separate slot for the reorder queue, and use ExecForceStoreHeapTuple() to store tuples from the queue. It's not particularly common to need reordering, after all. This reverts most of the iss_ReorderQueueSlot related changes to nodeIndexscan.c made in 1a0586de3657cd3, except that now ExecForceStoreHeapTuple() is used instead of ExecStoreHeapTuple(). Noticed when testing zheap against the in-core version of tableam. Author: Andres Freund
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions