Skip to content

Commit 0cafdd0

Browse files
committed
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 ff11e7f, so back-patch to v12 where that was added. Didier Gautheron Discussion: https://postgr.es/m/CAJRYxu+XQuM0qnSqt1Ujztu6fBPzMMAT3VEn6W32rgKG6A2Fsw@mail.gmail.com
1 parent 7bf40ea commit 0cafdd0

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/backend/commands/trigger.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2533,7 +2533,7 @@ ExecBRInsertTriggers(EState *estate, ResultRelInfo *relinfo,
25332533
TupleTableSlot *slot)
25342534
{
25352535
TriggerDesc *trigdesc = relinfo->ri_TrigDesc;
2536-
HeapTuplenewtuple = false;
2536+
HeapTuplenewtuple = NULL;
25372537
boolshould_free;
25382538
TriggerData LocTriggerData;
25392539
inti;
@@ -3178,7 +3178,7 @@ ExecIRUpdateTriggers(EState *estate, ResultRelInfo *relinfo,
31783178
{
31793179
TriggerDesc *trigdesc = relinfo->ri_TrigDesc;
31803180
TupleTableSlot *oldslot = ExecGetTriggerOldSlot(estate, relinfo);
3181-
HeapTuplenewtuple = false;
3181+
HeapTuplenewtuple = NULL;
31823182
boolshould_free;
31833183
TriggerData LocTriggerData;
31843184
inti;

0 commit comments

Comments
 (0)