From 5963b29e03d9b93011acb3954ccc3565d217acc3 Mon Sep 17 00:00:00 2001 From: Andres Freund Date: Wed, 27 Feb 2019 09:14:34 -0800 Subject: [PATCH] Initialize variable to silence compiler warning. After ff11e7f4b9ae Tom's compiler warns about accessing a potentially uninitialized rInfo. That's not actually possible, but it's understandable the compiler would get this wrong. NULL initialize too. Reported-By: Tom Lane Discussion: https://postgr.es/m/11199.1551285318@sss.pgh.pa.us --- src/backend/commands/trigger.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/backend/commands/trigger.c b/src/backend/commands/trigger.c index c5e588e801..7109889694 100644 --- a/src/backend/commands/trigger.c +++ b/src/backend/commands/trigger.c @@ -4490,7 +4490,7 @@ afterTriggerInvokeEvents(AfterTriggerEventList *events, AfterTriggerEventChunk *chunk; MemoryContext per_tuple_context; bool local_estate = false; - ResultRelInfo *rInfo; + ResultRelInfo *rInfo = NULL; Relation rel = NULL; TriggerDesc *trigdesc = NULL; FmgrInfo *finfo = NULL; -- 2.40.0