aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeLockRows.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2019-02-28 13:55:27 -0800
committerAndres Freund <andres@anarazel.de>2019-02-28 14:54:12 -0800
commit8f0577386e68c3b1c83a07b95756e5ee3f4ae73f (patch)
treed83f5e6daed6cbf07ec0fffb1bb826f544ab3e94 /src/backend/executor/nodeLockRows.c
parent2c31825fb9a95914418f1e376917f60841a26c78 (diff)
downloadpostgresql-8f0577386e68c3b1c83a07b95756e5ee3f4ae73f.tar.gz
postgresql-8f0577386e68c3b1c83a07b95756e5ee3f4ae73f.zip
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
Diffstat (limited to 'src/backend/executor/nodeLockRows.c')
0 files changed, 0 insertions, 0 deletions