Does TupleQueueReaderNext() really need to copy its result?

Applying: Avoid redundant tuple copy while sending tuples to Gather
Using index info to reconstruct a base tree...
M	src/backend/executor/execTuples.c
M	src/backend/executor/tqueue.c
M	src/include/executor/tuptable.h
Falling back to patching base and 3-way merge...
Auto-merging src/include/executor/tuptable.h
Auto-merging src/backend/executor/tqueue.c
CONFLICT (content): Merge conflict in src/backend/executor/tqueue.c
Auto-merging src/backend/executor/execTuples.c
Patch failed at 0001 Avoid redundant tuple copy while sending tuples to Gather

error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"