Suspicious redundant assignment in COPY FROM
Hi all, I was reading code of COPY FROM and I found some suspicious
redundant assignment for tuple descriptor and number of attributes. Is
it a behavior on purpose, or an accidently involved by the refactor in
c532d15? Patch is attached.
Attachments:
0001-Remove-redundant-assignment-in-copyfrom.patchapplication/octet-stream; name=0001-Remove-redundant-assignment-in-copyfrom.patchDownload+1-5
On Fri, Sep 08, 2023 at 12:23:17PM +0800, Jingtang Zhang wrote:
Hi all, I was reading code of COPY FROM and I found some suspicious
redundant assignment for tuple descriptor and number of attributes. Is
it a behavior on purpose, or an accidently involved by the refactor in
c532d15? Patch is attached.
This looks like a copy-pasto to me, as the tuple descriptor coming
from the relation is just used for sanity checks on the attributes
depending on the options by the caller for the COPY.
The assignment of num_phys_attrs could be kept at the same place as
on HEAD, a bit closer to the palloc0() where it is used.
--
Michael
Michael Paquier <michael@paquier.xyz> 于2023年9月8日周五 13:42写道：
Thanks, Michael~
The assignment of num_phys_attrs could be kept at the same place as
on HEAD, a bit closer to the palloc0() where it is used.
Agreed with this principle. Patch is modified and attached.
--
Jingtang