From: Stephen Frost Date: Thu, 10 Sep 2015 13:22:38 +0000 (-0400) Subject: Fix typo in setrefs.c X-Git-Tag: REL9_2_14~40 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f4ea1b35d56e84d7eb387a0226f6eed32a8a6cb4;p=postgresql Fix typo in setrefs.c We're adding OIDs, not TIDs, to invalItems. Pointed out by Etsuro Fujita. Back-patch to all supported branches. --- diff --git a/src/backend/optimizer/plan/setrefs.c b/src/backend/optimizer/plan/setrefs.c index 5732e2015e..3181ce6977 100644 --- a/src/backend/optimizer/plan/setrefs.c +++ b/src/backend/optimizer/plan/setrefs.c @@ -915,7 +915,7 @@ copyVar(Var *var) * This is code that is common to all variants of expression-fixing. * We must look up operator opcode info for OpExpr and related nodes, * add OIDs from regclass Const nodes into root->glob->relationOids, and - * add catalog TIDs for user-defined functions into root->glob->invalItems. + * add catalog OIDs for user-defined functions into root->glob->invalItems. * * We assume it's okay to update opcode info in-place. So this could possibly * scribble on the planner's input data structures, but it's OK.