Skip to content

Commit 90abbba

Browse files
committed
Fix minor violations of FunctionCallInvoke usage protocol.
Working on commit 1c45507 led me to check through FunctionCallInvoke call sites to see if every one was being honest about (a) making sure that fcinfo.isnull is initially false, and (b) checking its state after the call. Sure enough, I found some violations. The main one is that finalize_partialaggregate re-used serialfn_fcinfo without resetting isnull, even though it clearly intends to cater for serialfns that return NULL. There would only be an issue with a non-strict serialfn, since it's unlikely that a serialfn would return NULL for non-null input. We have no non-strict serialfns in core, and there may be none in the wild either, which would account for the lack of complaints. Still, it's clearly wrong, so back-patch that fix to 9.6 where finalize_partialaggregate was introduced. Also, arrayfuncs.c and rowtypes.c contained various callers that were not bothering to check for result nulls. While what's being called is a comparison or hash function that probably *shouldn't* return null, that's a lousy excuse for not having any check at all. There are existing places that just Assert(!fcinfo->isnull) in comparable situations, so I added that to the places that were calling btree comparison or hash support functions. In the places calling boolean-returning equality functions, it's quite cheap to have them treat isnull as FALSE, so make those places do that. Also remove some "locfcinfo->isnull = false" assignments that are unnecessary given the assumption that no previous call returned null. These changes seem like mostly neatnik-ism or debugging support, so I didn't back-patch.
1 parent e26c8a6 commit 90abbba

File tree

2 files changed

+6
-0
lines changed

2 files changed

+6
-0
lines changed

src/backend/executor/nodeAgg.c

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1014,6 +1014,7 @@ finalize_partialaggregate(AggState *aggstate,
10141014
pergroupstate->transValueIsNull,
10151015
pertrans->transtypeLen);
10161016
fcinfo->args[0].isnull = pergroupstate->transValueIsNull;
1017+
fcinfo->isnull = false;
10171018

10181019
*resultVal = FunctionCallInvoke(fcinfo);
10191020
*resultIsNull = fcinfo->isnull;

src/include/fmgr.h

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -163,6 +163,11 @@ extern void fmgr_symbol(Oid functionId, char **mod, char **fn);
163163
* caller must still check fcinfo->isnull! Also, if function is strict,
164164
* it is caller's responsibility to verify that no null arguments are present
165165
* before calling.
166+
*
167+
* Some code performs multiple calls without redoing InitFunctionCallInfoData,
168+
* possibly altering the argument values. This is okay, but be sure to reset
169+
* the fcinfo->isnull flag before each call, since callees are permitted to
170+
* assume that starts out false.
166171
*/
167172
#define FunctionCallInvoke(fcinfo) ((* (fcinfo)->flinfo->fn_addr) (fcinfo))
168173

0 commit comments

Comments
 (0)