projects
/
users
/
simon
/
postgres.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
| inline |
side by side
(parent:
e9c8b60
)
Add comment about why "((void) 0)" is used in copy macros.
author
Bruce Momjian
<bruce@momjian.us>
Wed, 3 Jun 2009 14:48:33 +0000
(14:48 +0000)
committer
Bruce Momjian
<bruce@momjian.us>
Wed, 3 Jun 2009 14:48:33 +0000
(14:48 +0000)
src/backend/commands/copy.c
patch
|
blob
|
blame
|
history
diff --git
a/src/backend/commands/copy.c
b/src/backend/commands/copy.c
index 1460edcf9b4e28c5be6d74b066f6a0e78bef6fbf..2acdf46d2f8f5a0f289c05651292d76e849badc4 100644
(file)
--- a/
src/backend/commands/copy.c
+++ b/
src/backend/commands/copy.c
@@
-175,7
+175,8
@@
typedef struct
/*
* These macros centralize code used to process line_buf and raw_buf buffers.
* They are macros because they often do continue/break control and to avoid
- * function call overhead in tight COPY loops.
+ * function call overhead in tight COPY loops. "((void) 0)" is used to silence
+ * compiler warnings.
*
* We must use "if (1)" because "do {} while(0)" overrides the continue/break
* processing. See http://www.cit.gu.edu.au/~anthony/info/C/C.macros.