Fix silly initializations (cosmetic only).
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 13 Nov 2019 20:26:54 +0000 (15:26 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 13 Nov 2019 20:26:54 +0000 (15:26 -0500)
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

index 84144b46b15b705bf95a90e852a4e85e51a6cfca..8d22d43bc3a7ceade3f73cd54d6f115c92840394 100644 (file)
@@ -2533,7 +2533,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;
@@ -3178,7 +3178,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;