Hi, On 2020-04-09 16:22:11 -0700, Jesse Zhang wrote: > We found that several functions -- namely numeric_combine, > numeric_avg_combine, numeric_poly_combine, and int8_avg_combine -- are > returning NULL without signaling the nullity of datum in fcinfo.isnull. > This is obscured by the fact that the only functions in core (finalfunc > for various aggregates) that those return values feed into happen to > tolerate (or rather, not quite distinguish) zero-but-not-NULL trans > values.
Shouldn't these just be marked as strict? Greetings, Andres Freund