Commit0cafdd0

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'venot seen any such warnings in the buildfarm).Seems to have come in with commitff11e7f, so back-patchto v12 where that was added.Didier GautheronDiscussion:https://postgr.es/m/CAJRYxu+XQuM0qnSqt1Ujztu6fBPzMMAT3VEn6W32rgKG6A2Fsw@mail.gmail.com

1 parent7bf40ea commit0cafdd0Copy full SHA for 0cafdd0

File tree

-2

lines changed

-2

lines changed

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -2533,7 +2533,7 @@ ExecBRInsertTriggers(EState estate, ResultRelInfo relinfo,`
`2533`	`2533`	`TupleTableSlot*slot)`
`2534`	`2534`	`{`
`2535`	`2535`	`TriggerDesc*trigdesc=relinfo->ri_TrigDesc;`
`2536`		`-HeapTuplenewtuple=false;`
	`2536`	`+HeapTuplenewtuple=NULL;`
`2537`	`2537`	`boolshould_free;`
`2538`	`2538`	`TriggerDataLocTriggerData;`
`2539`	`2539`	`inti;`
`@@ -3178,7 +3178,7 @@ ExecIRUpdateTriggers(EState estate, ResultRelInfo relinfo,`
`3178`	`3178`	`{`
`3179`	`3179`	`TriggerDesc*trigdesc=relinfo->ri_TrigDesc;`
`3180`	`3180`	`TupleTableSlot*oldslot=ExecGetTriggerOldSlot(estate,relinfo);`
`3181`		`-HeapTuplenewtuple=false;`
	`3181`	`+HeapTuplenewtuple=NULL;`
`3182`	`3182`	`boolshould_free;`
`3183`	`3183`	`TriggerDataLocTriggerData;`
`3184`	`3184`	`inti;`

Comments

(0)