Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit101f903

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

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

‎src/backend/commands/copy.c

Lines changed: 3 additions & 0 deletions
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
staticinlineTupleTableSlot*
26092612
CopyMultiInsertInfoNextFreeSlot(CopyMultiInsertInfo*miinfo,

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp