Skip to content

Commit 101f903

Browse files
committed
Add comment to explain an unused function parameter
Removing the unused 'miinfo' parameter has been raised a couple of times now. It was decided in the 2nd discussion below that we're going to leave it alone. It seems like it might be useful to add a comment to mention this fact so that nobody wastes any time in the future proposing its removal again. Discussion: https://postgr.es/m/CAApHDvpCf-qR5HC1rXskUM4ToV+3YDb4-n1meY=vpAHsRS_1PA@mail.gmail.com Discussion: https://postgr.es/m/CAE9k0P%3DFvcDswnSVtRpSyZMpcAWC%3DGp%3DifZ0HdfPaRQ%3D__LBtw%40mail.gmail.com
1 parent f1fcf2d commit 101f903

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

src/backend/commands/copy.c

+3
Original file line numberDiff line numberDiff line change
@@ -2604,6 +2604,9 @@ CopyMultiInsertInfoCleanup(CopyMultiInsertInfo *miinfo)
26042604
* Get the next TupleTableSlot that the next tuple should be stored in.
26052605
*
26062606
* Callers must ensure that the buffer is not full.
2607+
*
2608+
* Note: 'miinfo' is unused but has been included for consistency with the
2609+
* other functions in this area.
26072610
*/
26082611
static inline TupleTableSlot *
26092612
CopyMultiInsertInfoNextFreeSlot(CopyMultiInsertInfo *miinfo,

0 commit comments

Comments
 (0)