Re: Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot() - Mailing list pgsql-hackers

From David Rowley
Subject Re: Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()
Date
Msg-id CAKJS1f-A5aYvPHe10Wy9LjC4RzLsBrya8b2gfuQHFabhwZT_NQ@mail.gmail.com
Whole thread Raw
In response to Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()  (Ashutosh Sharma <ashu.coek88@gmail.com>)
Responses Re: Passing CopyMultiInsertInfo structure to CopyMultiInsertInfoNextFreeSlot()  (Ashutosh Sharma <ashu.coek88@gmail.com>)
List pgsql-hackers
On Mon, 13 May 2019 at 23:20, Ashutosh Sharma <ashu.coek88@gmail.com> wrote:
> In the latest PostgreSQL code, I could see that we are passing CopyMultiInsertInfo structure to
CopyMultiInsertInfoNextFreeSlot()although it is not being used anywhere in that function. Could you please let me know
ifit has been done intentionally or it is just an overlook that needs to be corrected. AFAIU,
CopyMultiInsertInfoNextFreeSlot()is just intended to return the next free slot available in the multi insert buffer and
wealready have that buffer stored in ResultRelInfo structure which is also being passed to that function so not sure
whatcould be the purpose of passing CopyMultiInsertInfo structure as well. Please let me know if i am missing something
here.Thank you. 

There's likely no good reason for that. The attached removes it.

--
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PANIC :Call AbortTransaction when transaction id is no normal
Next
From: Kuntal Ghosh
Date:
Subject: Re: PANIC :Call AbortTransaction when transaction id is no normal