postgres.git / summary / log / commit / refs

commit    6d36d7b63f298a335f495c579cdcde903b4e0645
Author:   Tom Lane <tgl@sss.pgh.pa.us>
Date:     Thu Sep 10 14:26:58 2015 +0000
First released in: 9.0.23, 9.1.19

    Revert "Fix typo in setrefs.c"
    
    This reverts commit 0473e047877ab9e51d5130bc14276b2308ed77a8.


 src/backend/optimizer/plan/setrefs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/backend/optimizer/plan/setrefs.c b/src/backend/optimizer/plan/setrefs.c
index 0e2d1caa02f..2e1c045ea80 100644
--- a/src/backend/optimizer/plan/setrefs.c
+++ b/src/backend/optimizer/plan/setrefs.c
@@ -765,7 +765,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 glob->relationOids,
- * and add catalog OIDs for user-defined functions into glob->invalItems.
+ * and add catalog TIDs for user-defined functions into 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.


[parent: 0473e047877a]