-
- Downloads
I had overlooked the fact that some fmgr-callable functions return void
--- ie, they're only called for side-effects. Add a PG_RETURN_VOID() macro and use it where appropriate. This probably doesn't change the machine code by a single bit ... it's just for documentation.
Showing
- src/backend/access/gist/gist.c 3 additions, 3 deletionssrc/backend/access/gist/gist.c
- src/backend/access/gist/gistscan.c 4 additions, 4 deletionssrc/backend/access/gist/gistscan.c
- src/backend/access/hash/hash.c 7 additions, 7 deletionssrc/backend/access/hash/hash.c
- src/backend/access/nbtree/nbtree.c 7 additions, 7 deletionssrc/backend/access/nbtree/nbtree.c
- src/backend/access/rtree/rtproc.c 3 additions, 4 deletionssrc/backend/access/rtree/rtproc.c
- src/backend/access/rtree/rtree.c 3 additions, 3 deletionssrc/backend/access/rtree/rtree.c
- src/backend/access/rtree/rtscan.c 5 additions, 5 deletionssrc/backend/access/rtree/rtscan.c
- src/backend/utils/adt/arrayfuncs.c 3 additions, 6 deletionssrc/backend/utils/adt/arrayfuncs.c
- src/backend/utils/adt/selfuncs.c 2 additions, 3 deletionssrc/backend/utils/adt/selfuncs.c
- src/include/fmgr.h 4 additions, 1 deletionsrc/include/fmgr.h
Loading
Please register or sign in to comment