Hi, On 2018-01-29 15:16:59 -0500, Tom Lane wrote: > > Also zero-initialize all scratch ExprEvalStep's allocated on the > > stack, to avoid issues with similar future omissions of non-critial > > data. > > Dunno that that's a good idea; it will also serve to hide valid warnings.
Possible, but I think it's more likely that new fields with default to zero/NULL anyway. Zero initializing around allocations is a pretty common thing in the PG codebase, so it does feel consistent to me. Greetings, Andres Freund
