mirror of
https://github.com/postgres/postgres.git
synced 2025-06-13 07:41:39 +03:00
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.
This commit is contained in:
@ -8,7 +8,7 @@
|
||||
*
|
||||
*
|
||||
* IDENTIFICATION
|
||||
* $Header: /cvsroot/pgsql/src/backend/access/rtree/Attic/rtree.c,v 1.48 2000/06/13 07:34:49 tgl Exp $
|
||||
* $Header: /cvsroot/pgsql/src/backend/access/rtree/Attic/rtree.c,v 1.49 2000/06/14 05:24:43 tgl Exp $
|
||||
*
|
||||
*-------------------------------------------------------------------------
|
||||
*/
|
||||
@ -281,7 +281,7 @@ rtbuild(PG_FUNCTION_ARGS)
|
||||
pfree(nulls);
|
||||
pfree(d);
|
||||
|
||||
PG_RETURN_POINTER(NULL); /* no real return value */
|
||||
PG_RETURN_VOID();
|
||||
}
|
||||
|
||||
/*
|
||||
@ -1025,7 +1025,7 @@ rtdelete(PG_FUNCTION_ARGS)
|
||||
|
||||
WriteBuffer(buf);
|
||||
|
||||
PG_RETURN_POINTER(NULL); /* no real return value */
|
||||
PG_RETURN_VOID();
|
||||
}
|
||||
|
||||
static void
|
||||
|
Reference in New Issue
Block a user