From 99cc47b1d85aabc4a80910c839073f83a4fb163b Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Wed, 13 Nov 2019 15:26:54 -0500 Subject: [PATCH] Fix silly initializations (cosmetic only). Initializing a pointer to "false" isn't per project style, and reportedly some compilers warn about it (though I've not seen any such warnings in the buildfarm). Seems to have come in with commit ff11e7f4b, so back-patch to v12 where that was added. Didier Gautheron Discussion: https://postgr.es/m/CAJRYxu+XQuM0qnSqt1Ujztu6fBPzMMAT3VEn6W32rgKG6A2Fsw@mail.gmail.com --- src/backend/commands/trigger.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/commands/trigger.c b/src/backend/commands/trigger.c index e2048c19f79..21719c0bb12 100644 --- a/src/backend/commands/trigger.c +++ b/src/backend/commands/trigger.c @@ -2536,7 +2536,7 @@ ExecBRInsertTriggers(EState *estate, ResultRelInfo *relinfo, TupleTableSlot *slot) { TriggerDesc *trigdesc = relinfo->ri_TrigDesc; - HeapTuple newtuple = false; + HeapTuple newtuple = NULL; bool should_free; TriggerData LocTriggerData; int i; @@ -3181,7 +3181,7 @@ ExecIRUpdateTriggers(EState *estate, ResultRelInfo *relinfo, { TriggerDesc *trigdesc = relinfo->ri_TrigDesc; TupleTableSlot *oldslot = ExecGetTriggerOldSlot(estate, relinfo); - HeapTuple newtuple = false; + HeapTuple newtuple = NULL; bool should_free; TriggerData LocTriggerData; int i;