]> granicus.if.org Git - postgresql/commit
Don't force materializing when copying a buffer tuple table slot.
authorAndres Freund <andres@anarazel.de>
Thu, 28 Feb 2019 21:55:27 +0000 (13:55 -0800)
committerAndres Freund <andres@anarazel.de>
Thu, 28 Feb 2019 22:54:12 +0000 (14:54 -0800)
commit8f0577386e68c3b1c83a07b95756e5ee3f4ae73f
treed83f5e6daed6cbf07ec0fffb1bb826f544ab3e94
parent2c31825fb9a95914418f1e376917f60841a26c78
Don't force materializing when copying a buffer tuple table slot.

After 5408e233f0667478 it's not necessary to force materializing the
target slot when copying from one buffer slot to another. Previously
that was required because the HeapTupleData portion of the source slot
wasn't guaranteed to stay valid long enough, but now we can simply
copy that part into the destination slot's tupdata.

Author: Andres Freund
src/backend/executor/execTuples.c